I'm experiencing a delay on some of my workflows, when they start. The thing that happens is that an item is changed, which should start the workflow, does not start the workflow right after. But when the clock hits the minute count 00 05 10 15 20 25 30 35 40 45 50 or 55, the workflow starts and works as it should. I guess it's the workflow engine/timer that kicks in and starts the workflow.
It seems that this mostly (or only?) happens, when one workflow makes a change to an item, that causes another workflow to start. But I have also seen this scenario, where the second workflow starts right after the first workflow has made it's changes to the item.
I have read this article, but it does not explain the delayed start and also, I don't use any of the listed actions, that will cause a delay within a workflow.
So my two questions are:
What can cause a workflow to start with this delay?
What can I do to prevent this?
Running Ninext Workflow 2013 on premise.