Skip to main content

I have an event on customer order creation that calls a workflow.  This is NOT setup as a projection action, but an actual event.  It works fine when I just go to the customer order screen, hit new, and save.  However, if the order is created via a background job or created via an interface like external customer order with auto approval, the workflow never fires.  I was wondering if I need to grant the workflow to a permission set or something.  Anyone run into this?

If the event happens due to a change from the background job the timing in the workflow needs to be set to 'Asynchronous’ for the workflow to trigger. 

 

Thanks for your response.  However,  I did set to Asynchronous and it’s still not firing.  Here is the event action which is on the CUSTOMER_ORDER_TAB new record:

Here’s the workflow.  It’s pretty basic:

As I’ve said, this works fine when you hit new on the customer order page and save.  Any other ideas?

Reply


Terms & ConditionsCookie settings