# Time violation in cyclic task

**URL:** <https://community.br-automation.com/t/time-violation-in-cyclic-task/8855>\
**Category:** B&R Software & Runtime\
**Tags:** automation-runtime, plc\
**Created:** [October 30, 2025, 1:55pm UTC](https://community.br-automation.com/t/time-violation-in-cyclic-task/8855 "2025-10-30T13:55:22Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pavel.vavra](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/pavel.vavra/32/9893_2.png) [@pavel.vavra](https://community.br-automation.com/u/pavel.vavra)\
**Post date:** [October 31, 2025, 4:57am UTC](https://community.br-automation.com/t/time-violation-in-cyclic-task/8855/2 "2025-10-31T04:57:22Z")

</div>

Hello and welcome to the Community,

The best way to diagnose cycle time violations is with [displaying profiler data as a diagram](https://help.br-automation.com/#/en/4/diagnostics_support/diagnosis/profile/analyze/graphic/diagnosis_profile_analyze_graphic.html). You should see what delays an execution and is a reason for the ArException. Be sure to set up the profiler correctly before the error happens; see [How to create a long profiler with enough data for analysis](https://community.br-automation.com/t/how-to-create-a-long-profiler-with-enough-data-for-analysis/493) Community topic.

It’s also a good idea to check normal (average) CPU usage (either with profiler or with [SDM](https://help.br-automation.com/#/en/4/automationruntime/targets/sdm/sdm/sdm2_system_cpuusage.htm)). It could also be that the CPU is already on the edge and every little execution delay causes the cycle time violation.

---

_[View the full topic](https://community.br-automation.com/t/time-violation-in-cyclic-task/8855)._