I have a workflow in Nintex 2019 and it has to pause 5 minutes then send email notification, however nothing seems to be wrong but the notification are not sent, when I check the idle time, it’s always increasing which I think that could be the cause, every time a user complain of not receiving email notifications, I always have to restart the workflow and it works, is there a way to make the idle time less or stop the workflow from idling for too long, the below is a screenshot of a workflow that has not sent through notification, the pausing time has already lapsed and notification are not sent.
Nintex for SharePoint uses SharePoint's workflow engine, so it doesn't matter if the workflow was created by Nintex or in SharePoint Designer, etc. After a workflow is paused, it resumes in SharePoints workflow timer service. If this service is busy or not functioning correctly, the workflow will keep waiting to resume. As this issue happens intermittently, the timer service is likely getting overwhelmed at certain parts of the day. Check what else is running on the service and when it's running so that you can spread the load. If the issue persists, you can contact Nintex Support for some tips and tricks, but ultimately, you may need to seek support from Microsoft.
Thank you Simon, the issue was on the timer service, it had stopped.
Nintex for SharePoint uses SharePoint's workflow engine, so it doesn't matter if the workflow was created by Nintex or in SharePoint Designer, etc. After a workflow is paused, it resumes in SharePoints workflow timer service. If this service is busy or not functioning correctly, the workflow will keep waiting to resume. As this issue happens intermittently, the timer service is likely getting overwhelmed at certain parts of the day. Check what else is running on the service and when it's running so that you can spread the load. If the issue persists, you can contact Nintex Support for some tips and tricks, but ultimately, you may need to seek support from Microsoft.
Nintex for SharePoint uses SharePoint's workflow engine, so it doesn't matter if the workflow was created by Nintex or in SharePoint Designer, etc. After a workflow is paused, it resumes in SharePoints workflow timer service. If this service is busy or not functioning correctly, the workflow will keep waiting to resume. As this issue happens intermittently, the timer service is likely getting overwhelmed at certain parts of the day. Check what else is running on the service and when it's running so that you can spread the load. If the issue persists, you can contact Nintex Support for some tips and tricks, but ultimately, you may need to seek support from Microsoft.
Thank you Simon, the issue was on the timer service, it had stopped.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
