Fixes for Common Issues and Errors
View All Tags
The Power Platform CLI signed me in without a problem, and the very next command failed: No active environment set for the current auth profile. The sign-in had created a profile with no environment attached. One command, pac env select, fixed it.
I set an environment variable's Export value to No and saved. When I opened the variable again, the switch said Yes, and the exported solution still held my SharePoint site's address. The switch can't be trusted on its own, the zip file is the real test, and the Power Platform CLI takes the values out.
I ran my setup flow a second time to prove it was safe to run again. Instead of finishing in seconds, it sat on Waiting for half an hour, then failed: Action 'Remove_Title_from_the_view' failed: BadGateway. Behind the 502 was SharePoint saying Invalid field name. The first run had already removed that column from the view, and asking again was an error that Power Automate retried for minutes at a time.
My flow failed with Invalid JSON. A token was not recognized in the JSON content. The JSON it sent looked fine in the designer. In the run, a false from my data had become False, with a capital F, which isn't JSON. An if() expression fixed it.
Power Automate's expression editor told me This expression has a problem. You can fix it manually or with Copilot. The expression was correct, and the same one worked elsewhere in the flow. Selecting Add again, sometimes two or three times, added it. Once, though, the message was right, and the reason is worth knowing.
I saved a cloud flow, and the action I had open in Power Automate's new designer suddenly showed No additional information is needed for this step, Not connected. and an empty Code view. It looked as if Save had wiped the action. It hadn't: selecting the action again brought everything back.
I created a cloud flow from inside one solution, and the flow's details page said it belonged to two. The second one was my preferred solution. Microsoft documents why, and the fix moved the flow to a single solution without deleting anything.
I changed someone's job title in the Microsoft Entra admin center, got Successfully updated, and the Properties tab still showed the old title. The save had worked; the page hadn't caught up. Reloading the browser page fixed it.
When someone leaves, Microsoft's offboarding steps sign them out of everything and block their sign-in. I blocked first, and the Microsoft 365 admin center then stopped offering Sign out of all sessions. Microsoft Entra's Revoke sessions still worked.
On the narrowest phones, 360 pixels wide, my Power Apps app had three layout problems: a title cut in half, a button running off the screen, and list rows where a button left almost no room for the text. Each fix uses the screen's size, so phones get a tighter layout and larger screens stay as they were.
