Workflow - Transaction cancelled: maximum execution time exceededIssue Checking the workflow activity, we see below error in Workflow log : com.glide.sys.TransactionCancelledException: Transaction cancelled: maximum execution time exceeded Workflow 'XYZ' with context <context_sysid> terminated 2020-08-18 14:03:58 UTC with : Transaction cancelled: maximum execution time exceeded. Need to know why error "Transaction cancelled: maximum execution time exceeded" occurred and what is the reason behind the error though we are inserting records into a table asynchronously. To make it run asynchronously, 1 Second timer was added on the workflowCauseBased on the workflow context we see that activities executed after the timer activity are created and initiated from the user session itself.The activities executed after the timer activity is also created by shows as a user and not system. OOB behavior:While checking the same in OOB the timer was initiated by user session but after timer activity, the next activity was executed by the system and by worker.Ideally, when a timer is present, the transaction should be present running using a worker node.ResolutionChange the 1 second timers to 3 second timers to ensure the workflow actually sleeps and wakes up in the scheduled worker.It looks like the 1 second timers, in this instance, were evaluated and the end condition was now and thus didn't sleep the workflow. This is evident in the logs, the activity history was all done as the user, the script activity was canceled by the transaction quota, This is not readily reproducible, etc.This can happen for a number of reasons, typically, what happens is that when the timer activity starts, it is given the end time. The duration calculation that adds 1 second to now happens very first, then the activity definition code starts to execute. The activity checks the end time with now and if they are the same, the activity doesn't sleep the workflow, but just ends and the workflow moves on to the next activity.We've seen this on instances that have a heavy load, and thus takes a little longer to execute statements.