My workflow executes perfectly when I am an admin. When I execute the workflow as a different user with the custom apps security role it only creates 1 of the tasks.
I expect the workflow to always create 3 service tasks once initial ticket is created.
This is the example with my admin account - workflow executes properly
Below is What happens with the custom security role... The workflow initiates and creates 1 service task, but never creates the other 2.
Why would a Workflow stop after being initiated?
Hi @Austin Bedell ,
1)Do you see any errors when you execute as different user (check the flow context for errors\logs , check users have access to create tasks)
2)You can alos resolve this by setting run user as system user so that flow executes as system and create tasks despite of the users (users or admins)
Hi @Austin Bedell ,
1)Do you see any errors when you execute as different user (check the flow context for errors\logs , check users have access to create tasks)
2)You can alos resolve this by setting run user as system user so that flow executes as system and create tasks despite of the users (users or admins)
