Workflow timer taking excessive time, and as a result, the workflow is hungIssue The user had a Requested Item with a Timer workflow activity in it. The workflow was hung at the Timer activity for excessive amounts of time (e.g. the Timer was for 2 seconds, and the Timer was still processing after days).ResolutionIn this case, the issue was that the user had created a custom and recursive async Business Rule that backed up the event queue by over 10 million records.The reason this is impactful for workflow Timers is that when a workflow Timer activity executes in a workflow, a sys_trigger record is created with a "Next action" at the time when the Timer should end (current time + duration specified in the Timer activity = the "Next action" time). If the event queue is backed up with many sys_trigger jobs, workflow Timer sys_trigger records will not be able to perform the action at the correct "Next action" time - this will be delayed.