Hi Buddy,
This is usually a temporary Studio/source control sync issue on developer instances, not a problem with your code.
Ive seen those popups typically happen when Studio cant fully reconcile the app metadata during the commit/checkout job. Common causes are:
the background source control import/export job hasn’t completed yet (or retried after a timeout),
a transient network/API call issue to the Git provider on that PDI,
or the instance briefly treating the app as “store/customization-managed,” which triggers the “App Customization already exists…” message.
That also explains why it can “fix itself” later without doing anything — once the async jobs finish or the Git call succeeds, Studio becomes consistent again.
What you can do when it happens:
wait a minute and retry often enough to work
verify you’re on the correct repo/branch (the “no application file to import” error usually means Studio couldn’t find the app definition in that branch, or the import job failed),
if it keeps happening on one instance, unlink/relink source control (or re-checkout clean) to reset the local Studio state.
So yes — its typically underlying background processing and/or transient connectivity on PDIs rather than a permanent repo issue.
@Hetang Modi - If help you answer, Please mark Solution Accepted and Thumbs Up
MJG
