Nudges and Stuck Workflows

[jamesmcwhinney]

I have a workflow that seems to occasionally get stuck and needs a "nudge" to resume.
Does anyone have any insight as to why this might happen intermittently?

[Bharath40]

Hi James,

Can you elaborate some more, are you using any MID servers with powershell script in your workflow, we have this issue in our organization when MID server is down   , we have to restart or rerun making sure MID server is up.

[jamesmcwhinney]

Thanks Bharath, no mid servers or powershell scripts involved in this one unfortunately.

[andy_dufresne]

Hi James,

Were you able to figure out how to bypass this?

Thanks in advance!

[adam_foster99]

Hi James,

Does this help? It should "nudge" a workflow if you add it to a script:

new Workflow().broadcastEventToCurrentsContexts(<a GlideRecord>, 'update', null);

When you're waiting for a condition, I think the workflow won't always register that a record has been updated and the condition may now be true unless certain things happen. Can't remember what the criteria is for this (I last used this a long time ago!) but I remember this is how I got around it when one of my workflows needed a nudge.

You can find a little more information here: workflow.fireEvent is not allowed in scope Can't find anything in the docs right now, but it's probably in there somewhere.