Recently we have had the owner of a workflow leave the organisation. This has caused the workflow to stop working as expected. There is no option to change the Owner of the workflow in the UI, and when done via API it will show in the UI as expected, however the JSON from the workflow will still reference the old owner.
Can this be resolved to add an option to the UI to change the owner, and reflect in the JSON when done via UI or API to the new owner.
To resolve this, edit the workflow (ex. slightly change the description of a step) and save it, and that will cause the workflow to change owners to whomever edited it.
The Workflow team is aware of this and has a feature in the roadmap to make this transition more graceful.
Hello,
Is there any update on this known issue?
We are creating some new workflows and we want to see if it is possible to assign service accounts directly as owners of those workflows. Without having to login as service accounts and use the solution you mentioned.
It’s a low priority enhancement right now. There are higher priority items that are currently being worked on.
Given how the ownership model currently works, having a service account own these workflows could be problematic. As soon as another user modifies a workflow owned by an SA, the ownership will change to the user. There would be no mechanism to automatically change ownership back.
In the meantime, we can look into adding a command to the CLI to update the owner of one or more workflows via a simple command. Please comment on this issue if you have additional thoughts.