This should not be treated as a normal post-deployment activity. A Canvas App should not require someone to open it in Studio, refresh every table and flow,
save, and republish after every deployment.
The behavior strongly indicates a problem with Canvas App dependency resolution during ALM, most likely involving connection references, Power Automate
flow references, data-source bindings, or solution deployment/layering.
The most important clue is:
The app starts working immediately after manually refreshing data sources and flows and republishing.
That suggests the deployed app contains stale or unresolved dependency metadata. The manual refresh is effectively forcing Power Apps Studio to rebuild those
references.
this happens consistently after every deployment, I would also capture the solution version, Canvas App version, flow IDs, connection-reference mappings,
deployment logs, and exact runtime errors and raise it with Microsoft if the ALM configuration checks out. The repeated "refresh in Studio fixes it" behavior is a
particularly useful reproduction detail for Microsoft Support.
