Hi, @Kevin Nguyen ,
To say it short , SharePoint attempts to run Workflows synchronously. When the farm is experiencing a heavy load, say, the number of workflows exceeds 15 per content database (it is a default setting which can be tuned), the workflows will be converted to SPWorkItems and queued. This queue is then handled by the Workflow Timer Job, which runs every 5 minutes by default. The workflow Timer Job is ran by SharePoint Timer Service and by default will be triggered every 5 minutes as you mention. It will tries to run the work items later .
The workflow SPTimer job fires to process pending workflow tasks. This 5 minutes interval also represents the granularity of delay timers within your workflow. If a timer is set to delay for one minute, but the interval timer fires only every five minutes, the workflow delays for five minutes, not one minute.
Reference:https://www.softlanding.ca/blog/tuning-sharepoint-workflow-engine/#:~:text=library%2Fgg508755.aspx-,Summary,every%205%20minutes%20by%20default.
Workflows, by their very nature, do not execute in a nonstop, linear fashion. Instead, they run for a little while, pause, run some more, and then pause again, continuing in this manner until the process is complete.
More detailed information about the process, please refer to this article: https://learn.microsoft.com/en-us/previous-versions/office/developer/sharepoint-services/dd441390(v=office.12)?redirectedfrom=MSDN#WorkflowScalabilityPerformance_HardwareSoftwareConfig
And Nintex workflow is out of the scope of this forum, I am not certain if the mechanism of default workflow can be applied to Nintex ones, still you can take them as a reference.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.