Skip to content
DataMiner Dojo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Tutorials
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • YouTube Videos
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Agility
      • Learn more about Agile
        • Agile Webspace
        • Everything Agile
          • The Agile Manifesto
          • Best Practices
          • Retro Recipes
        • Methodologies
          • The Scrum Framework
          • Kanban
          • Extreme Programming
        • Roles
          • The Product Owner
          • The Agile Coach
          • The Quality & UX Coach (QX)
      • Book your Agile Fundamentals training
      • Book your Kanban workshop
    • >> Go to DataMiner Docs
  • DevOps
    • About the DevOps Program
    • Sign up for the DevOps Program
    • DataMiner DevOps Support
    • Feature Suggestions
  • Downloads
  • Swag Shop
  • PARTNERS
    • Business Partners
    • Technology Partners
  • Contact
    • Sales, Training & Certification
    • DataMiner Support
    • Global Feedback Survey
  • >> Go to dataminer.services

Communication State – Timeout hysteresis

257 views11th May 2026
4
Mariana Navarro [DevOps Advocate]384 6th May 2026 0 Comments

Hello Dojo!

Some of our AppearTV X20 Platform elements are intermittently entering and leaving the Communication – Timeout alarm state. The alarm raises and clears within the same second.

I expected that configuring the “The element goes into timeout state when it is not responding for:” field on the element edit page would prevent this behaviour, but it does not appear to be taking effect in this case.

Could you please advise on the correct way to configure timeout alarm hysteresis to avoid these brief timeout alarms?

Mariana Navarro [DevOps Advocate] Answered question 11th May 2026

2 Answers

  • Active
  • Voted
  • Newest
  • Oldest
2
Wouter Bogaert [SLC] [DevOps Enabler]1.20K Posted 6th May 2026 0 Comments

Hi Mariana, I believe the configuration does take effect, and we should look further into what exactly is causing the timeout. It could happen that a series of requests are not getting a response, eventually causing the timeout after 60s but the next request does get a response, resulting in this brief timeout alarm. To get a better understanding of the problem, can you open the Streamviewer on the element and let it capture until a timeout has passed? You should be able to spot which requests are timing out.

Wouter Bogaert [SLC] [DevOps Enabler] Answered question 6th May 2026
0
Mariana Navarro [DevOps Advocate]384 Posted 11th May 2026 0 Comments

Hello Wouter, sorry for the delay in the response. I got a Timeout alarm at 16:10:44, which just like the other ones also cleared at 16:10:44.

I was able to find some errors in the stream viewer, bare with me while I try to describe them:

The errors are all inside "Group 3 > Session 2 > Connection 1"

I got the following timeout errors inside the [Error_Code] page:

-> 16:06:36 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:08:44 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:09:32 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:09:44 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:10:52 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:10:56 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:11:00 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:13:00 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:13:04 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:13:08 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:14:44 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:14:48 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:14:52 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:15:16 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:15:20 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:17:24 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:17:28 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:19:32 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:19:36 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:19:40 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:19:44 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:21:32 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:21:36 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:21:48 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:23:36 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:23:40 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:23:44 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:23:48 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:24:44 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:24:48 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:24:52 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:25:52 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:25:56 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:28:00 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:28:04 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:29:48 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:29:52 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:30:20 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:30:24 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:32:28 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:32:32 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:34:36 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:34:40 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:35:04 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:35:08 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:35:12 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:36:36 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:38:44 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:38:48 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:40:04 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:40:08 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:40:12 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:40:56 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:41:00 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:41:04 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:43:04 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:43:08 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:43:12 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:45:12 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:45:16 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:45:20 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:45:36 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:45:40 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:45:44 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:47:28 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:47:32 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:49:36 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:49:40 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:50:16 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:50:20 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:50:24 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:50:28 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:51:28 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:51:32 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:53:36 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:53:40 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:53:44 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:55:24 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:55:28 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:55:32 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:55:52 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:55:56 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:56:00 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:58:04 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 16:58:08 - Error : 12002. [ERROR_WINHTTP_TIMEOUT] -> 17:00:16 - Error : 12002. [ERROR_WINHTTP_TIMEOUT]

I also got intermittently Bad Gateway [Status_Code] back, although no 408 Request Timeout in this page. I although I do see a very suspicious 401 Unauthorized not too long before the timeout alarm:

> 16:09:39 - HTTP/1.1 200 OK
-> 16:09:39 - HTTP/1.1 200 OK
-> 16:09:42 - HTTP/1.1 502 Bad Gateway
-> 16:09:42 - HTTP/1.1 200 OK
-> 16:09:43 - HTTP/1.1 200 OK
-> 16:09:43 - HTTP/1.1 200 OK
-> 16:09:46 - HTTP/1.1 502 Bad Gateway
-> 16:09:46 - HTTP/1.1 401 Unauthorized
-> 16:10:46 - HTTP/1.1 200 OK
-> 16:10:46 - HTTP/1.1 200 OK
-> 16:10:46 - HTTP/1.1 200 OK
-> 16:10:46 - HTTP/1.1 200 OK
-> 16:10:46 - HTTP/1.1 200 OK
-> 16:10:46 - HTTP/1.1 200 OK
-> 16:10:47 - HTTP/1.1 200 OK
-> 16:10:47 - HTTP/1.1 200 OK
-> 16:10:47 - HTTP/1.1 200 OK
-> 16:10:47 - HTTP/1.1 200 OK
-> 16:10:47 - HTTP/1.1 200 OK
-> 16:10:50 - HTTP/1.1 502 Bad Gateway
-> 16:10:50 - HTTP/1.1 200 OK
-> 16:10:50 - HTTP/1.1 200 OK
-> 16:10:50 - HTTP/1.1 200 OK
-> 16:10:53 - HTTP/1.1 502 Bad Gateway
-> 16:10:54 - HTTP/1.1 200 OK

The [Error_Code] page do have a lot of [ERROR_WINHTTP_TIMEOUT] logged, but I don't see anything special about the 16:10:44 which is the only alarm I got in this period, the last timeout alarm after that came at 09:55:40.

Mariana Navarro [DevOps Advocate] Answered question 11th May 2026
Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2026 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs

[ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin