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
    • Empower Replay: Limited Edition
    • 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
    • Video Library
    • Books We Like
    • >> Go to DataMiner Docs
  • Expert Center
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Markets & Industries
      • Media production
      • Government & defense
      • Content distribution
      • Service providers
      • Partners
      • OSS/BSS
    • 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)
    • DataMiner DevOps Professional Program
      • About the DevOps Program
      • DataMiner DevOps Support
  • Downloads
  • More
    • DataMiner Releases & Updates
    • Feature Suggestions
    • Climb the leaderboard!
    • Swag Shop
    • Contact
    • Global Feedback Survey
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Deal Registration
  • >> Go to dataminer.services

How to avoid Timed QAction be started on element connection?

Solved387 views3rd January 2025
4
JESUS PEREZ-ARANDA86 21st December 2024 3 Comments

Hi, I have an element created with a Timed Action wich should be executed every 4 hours,but  I see that everytime I connect with the element these QAction (and others) are also executed. Is theree any way to avoid these QActions to be executed on Element Connection?

Thanks

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 3rd January 2025
Thijs Vanovenacker [SLC] [DevOps Advocate] commented 21st December 2024

Hi, The behavior you describe doesn't sound normal. Could you please elaborate your question and include how your timer is defined in the protocol XML please?

Opening the element connection should by default not impact the execution of your timer group. Therefor my initial guess would be a wrong configuration or usage. Could it be that you configured the "DataDisplay" option on your timer? This would by design increase it's execution frequency when the elementcard is open. (https://docs.dataminer.services/develop/schemadoc/Protocol/Protocol.Timers.Timer.Time-dataDisplay.html)

Extra note: the time you define on your timer is defined in milliseconds.

Looking forward to some extra context, then we should be able to get you forward easily. Thanks!

JESUS PEREZ-ARANDA commented 22nd December 2024

thanks Thijs! that was the point, I had a datadisplay option set on the timer, deleting it solve the problem.

regards

Thijs Vanovenacker [SLC] [DevOps Advocate] commented 22nd December 2024

Great to hear that resolved your problem. I'll create an answer with my comment so we can close this item! Glad I could help!

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
3
Thijs Vanovenacker [SLC] [DevOps Advocate]2.21K Posted 22nd December 2024 2 Comments

Hi Jesus, The behavior you describe doesn't sound normal. Opening the element connection should by default not impact the execution of your timer group. Therefor my initial guess would be a wrong configuration or usage.

As confirmed via the comments, in your case you had configured the DataDisplay option on your timer configuration. This would by design increase it's execution frequency when the elementcard is open.

Removing this option should give the expected result you were aiming for.

Note that if you want to fully "fix" the timer speed, and not allow modifications via the Timer Base configuration (Changing the polling speed of an element | DataMiner Docs), you can define the option FixedTimer. Please see fixedTimer attribute | DataMiner Docs.

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 3rd January 2025
Tom Waterbley [SLC] [DevOps Catalyst] commented 23rd December 2024

When it's critical that the action is not being executed more frequently than every 4 hours, I would also recommend to store the last execution time in a parameter, and comparing it with the current time during the next execution. Otherwise the action would still be executed on, for example, an element restart.

José Silva [SLC] [DevOps Catalyst] commented 23rd December 2024

I agree with Tom. To strictly adhere to the 4-hour interval, it's best to save the time of the last execution in a parameter and compare it during the next execution. However, keep in mind that your timer should run at a faster interval to avoid missing the 4-hour execution window. For example, if the element restarts, a faster timer will ensure the check occurs promptly, preventing any gaps in execution.

You are viewing 1 out of 1 answers, click here to view all answers.
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

© 2025 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