Server not responsive after pending automation session

[petergrlica]

Api server becomes unresponsive when a specific workflow is triggered that puts it into an indefinite pending state.

To reproduce:
Create a simple workflow (afterUpdate) that calls a subworkflow
Inside the subworkflow use a function to notify a user

Once the workflow is executed, the user will not be notified, as the subworkflow does not get the user info.
The workflow will go into state pending and all further actions via rest api will be blocked.

Checklist:

• reproduce locally
• confirm subworkflow not getting user info

[petergrlica]

Not able to reproduce locally, checking on forum for some more info

[tjerman]

Failing to reproduce...
Tried triggering the "offending" workflow with another workflow.

Potential issue if the workflow has a run as?

[tjerman]

Asked for more info.
If the workflow has run as set; the result seems similar; it doesn't lock the server but it's the closest I managed to get.