'Run Trigger' button in Azure Portal always disabled for HTTP triggered workflows

[John-Bosch]

The 'Run Trigger' button is always blank on every one of my HTTP triggered workflows.

The button is enabled briefly while the Javascript loads, but as soon as the Workflow URL and other bits and pieces populate it is disabled.

If it helps, all of my logic apps are developed in VS Code and deployed via Azure Dev Ops.

[TWolverson]

I'm also encountering this. I once managed to snatch it quickly enough to create a run, thereafter it was greyed out.

The browser console sometimes logs a spurious error message relating to listing the LA's triggers, which I can't reproduce now. I notice that the Run Trigger button flashes enabled before the page is fully loaded, and greys out too fast to navigate to it.

Restarting the Logic App seems to sometimes bring it back, but it quickly disables again afterwards.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[John-Bosch]

Thanks Git-Bot. All you have to do is ignore an issue long enough and it goes away!

[hartra344]

Sorry, I'm slowly trying to get a handle on these issues and the github bot is helping me surface which issues are still issues. Thanks for responding 😄

As far as the issue, it looks like for this field we're conflating a permission check with a read only check of the app. Since you're using zip deploy as part of the ADO deployment, your workflow is in a read only state. I'm making a commit now to fix this. Should be in production in a couple weeks as part of the normal deployment process.

[John-Bosch]

Thank you for the update @hartra344. Thanks again for getting the fix in promptly.

[hartra344]

The fix for this has gone through testing and will be rolling out starting next week. Feel free to reopen if it's not fixed by Oct 8th