
Have you encountered an issue in Power Automate where your instant cloud flow, triggered by “For a selected file” or “For a selected item” deployed in a non-default environment, doesn’t show up in SharePoint? You’re not alone. This known bug has been reported since January 5, 2022, and unfortunately, there have been no updates to resolve it.
The main problem with this bug is that if your workflow is triggered by “For a selected file” or “For a selected item,” you won’t be able to use your non-default environment to host your workflow. This limitation means you won’t have the flexibility to have separate environments for testing or development.
To address this issue, follow these steps:
"$schema": "https://developer.microsoft.com/json-schemas/sp/v2/column-formatting.schema.json","elmType": "button","customRowAction": {"action": "executeFlow","actionParams": "{\"id\": \"[ENTER WORKFLOW IDENTIFIER HERE]\"}"},"attributes": {"class": "ms-fontColor-themePrimary ms-fontColor-teal"},"style": {"border": "none","background-color": "transparent","cursor": "pointer"},"children": [{"elmType": "span","attributes": {"iconName": "Flow"},"style": {"padding-right": "6px"}},{"elmType": "span","txtContent": "Start my Non Default Workflow"}]}
Replace [ENTER WORKFLOW IDENTIFIER HERE] with your own workflow identifier, which you can find on the Power Automate page.
Note: This example uses one of my workflows deployed to my non-default development environment.