Jump to content

Recommended Posts

Posted

We leverage several scheduled workflows to automate parts of our maintenance cycles. However we have noticed that when a workflow calls a 'Run Task' item it tries to run the task in the scope of the workflow rather than the scope assigned to the task itself. We resorted to tasks as a method of handling multiple scopes because workflows invoked from a scheduled workflow also run in the context of the calling scheduled workflow rather that its assigned scope. 

Please advise. 

  • Administrators
Posted

Hi @TheITJedi

So this is the expected behavior of the workflow, if you are looking to avail of the scopes attached to the task itself rather than the workflow your should focus on scheduling from tasks within the task scheduler, not the workflows. 

Let me know if this helps/makes sense and if you need any further assistance please let me know

image.thumb.png.e71864048acee23712a08e90551dfbe6.png

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...