Did you perhaps create multiple user accounts on your self hosted instance? Im suspecting that you are logged in as a different user than the original owner of the workflow. Typically this is a role based issue where only the owner of the workflow can publish
Hi @Wouter_Nigrini,
yes, I have multiple user accounts on my instance, but I’m logged in with the correct account, and this account is the owner of the workflow. When I log in with a different user and try to publish one of the workflows, I encounter the same issue. So, whenever the problem occurs, it affects all user accounts. Please note that I am using only the Community Edition and do not have a paid subscription.
I have exactly the same problem as the OP. After deployment, the Publish button is disabled, and the tooltip shows “You don’t have permission to publish this workflow.” After restarting the container, the problem is fixed. It’s very annoying.
Edit: Restarting only fixes the publishing issue the first time I restart it; now I restarted it and it stopped working again. I deployed it and restarted once more, and it still doesn’t work. Very strange.
I am also experiencing the same issue after updating from version 2.1.0 to 2.3.1.
After restarting, the Publish button becomes active, but when I try to publish, it fails with the message:
‘Workflow could not be published: User is missing a scope required to perform this action.’
Thanks for your feedback, in the moment I don’t had the problem again in version 2.2.6. I don’t know if the issue has fixed by it self or I’m very lucky since two days.