This points to a deep-linking failure between Business Central and Power Automate, not an issue with the flow logic.
The 404 in the widget means Business Central cannot resolve the environment or flow ID it is trying to load.
Most common causes: 1. Environment mismatch
The flow exists in a different Power Platform environment than the one mapped to your Business Central instance. 2. Broken flow reference
If the flow was recreated, moved, or reimported, its ID changes and BC continues pointing to an outdated reference. 3. Auth/session issues
The embedded widget depends on cross-domain auth. Expired or blocked tokens (cookies) can cause loading to hang.
What to do:
Confirm the flow exists in the same environment mapped to Business Central
Re-link the flow from the Automate menu (remove and add again)
Sign out, clear browser cache, and retry
Test in InPrivate/Incognito to isolate session issues
Summary:
A 404 here means Business Central cannot locate the flow in the expected environment, usually due to environment misalignment or stale flow references.
✅ If one of the responses here solved your issue, please mark it as Accepted so others facing the same problem can benefit as well.
👍 If this or any other reply here helped you, feel free to give it a Like. It helps others and is always appreciated.
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.