Workflow not triggering as expected

[bradfournier]

I have a team that requested new functionality for having an sms message sent if a ticket was not assigned to a user within 2 hours of it being sent to their team. I created a workflow that would trigger an event which in turn triggers the sms notification, however the workflow will not start and I can't figure out why. 

The workflow, the event, and the notification all live on the Task table. The workflow start conditions are in the first screenshot, and the workflow itself is shown in the second screenshot. When I create a test ticket and assign it to the 'Hardware SD' team with the assigned to field blank, the workflow does not start. 

Any suggestions would be helpful!

Thanks,
Brad

[bradfournier]

Hi Tony,

I have confirmed the basics. It is published; everything is in the same scope/application; the workflow, event, and notification are all built on the same table; there is only 1 group with that name. 

Thanks

[Tony Chatfield1]

Very odd indeed,
So the workflow doesn't trigger at all, no record of it in Active contexts, All contexts or Executing activities.
If you can export and attach a copy of the xml I'd be happy to take a closer look, although I'm not an expert in any shape\form.

The platform has been known to throw the odd curve ball, and about this point in time I'd normally try the quick fix - creating another version from scratch and\or simplify the trigger conditions to ensure it does run.

Regards Tony

[mmaraj1]

the only time ive known my workflow to not kick off entirely was when i did not select it in my(ex. catalog item ) so it was never linked ...

[bradfournier · Accepted solution]

So just to update, I did try to recreate another version of the workflow. However this time I built everything out from our Hardware Request table instead of from the Task table. Things seem to be working as intended now. Guess it doesn't like workflows running off the base Task table.