Hello and welcome to the Community,
The best way to diagnose cycle time violations is with displaying profiler data as a diagram. 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 Community topic.
It’s also a good idea to check normal (average) CPU usage (either with profiler or with SDM). It could also be that the CPU is already on the edge and every little execution delay causes the cycle time violation.