Workflows crashing

Hi Michael,

The o365 version can take a bit to get used to after having used on-prem for everything prior.  It really has been catching up over the past few years, but there are still some gaps.   When you say suspending - do you mean throwing an error?  The one thing about the online version is that it can start to queue up when too many requests are sent off which causes the workflow to essentially suspend (this can be caused by actions that loop continuously and result in too many requests).   This may not be what is happening in your case if a specific error is occurring, but I'd need a bit more detail to analyze it.

Thanks

Mike

Hi Michael,

When you come across a Suspended workflow instance, is there any error information logged in the notification bubble:

Typically this would be one of a few issues, such as a problem contacting SharePoint from the workflow, a problem contacting one of the Nintex services from the workflow, or a configuration problem. For some of the internal types of issues these messages are unfortunately not always useful (if it is an error in a Nintex service we will try to return the most useful information we can).

If you can share this info when a workflow has suspended either here or via DM we may be able to shed a bit more light on what is happening.

Regarding the notifications (of status change), unfortunately Workflow in SharePoint Online does not currently have any in-built notification/change events such as the ones that existed in the previous workflow engine ('SharePoint 2010 Workflow') that the Nintex On-Premises product uses.

Thanks,

Callum

Edit: You may or may not be aware of this page as well: Checking out the new Workflow Health pages | epmsource (It's not a notification but it does give a site wide status summary).