Vibe app went missing over the weekend?

(0) Share

Report

Posted on by TD-20041442-0

I published an app before the weekend, and the published version is still accessible. However, when I came back on Monday, I can’t find the app in Vibe.powerapps to edit it anymore.

There are three “Untitled” projects showing up, but when I try to open them, they return a 404 error (not sure if those are related). Nothing changed on my end over the weekend.

The app still exists in my environment, I can access the published version, and it shows that I’m the owner—but the editable version seems to be missing.

What could have caused this? Is this a known issue with Vibe? And is there a way to recover the app?

Categories:

Error handling

AI Builder

Building Power Apps

Experimental features

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Fredrik_A 3,631 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hey,

Vibe apps are in preview last time i checked so bugs like this can exist. Ive had the same issue when trying to do some PoCs where my app gets corrupted. You might be able to recreate the app via the same prompt if you can get it.

You can also try clearing your browser cache to see if that makes any difference.

And if none of above work, you can try making a ticket to Microsoft via the Power Platform admin center in your tenant and see if they are able to help you further.

If my response solved your issue, please mark it as ✅ Accepted Answer and give it a like.

Was this reply helpful? Yes No
Suggested answer

11manish 1,422 on at

Like (0)

Report
Copy link

Link copied!

This is most likely a Power Apps studio (Vibe) issue rather than actual data loss.

Since the published app is still accessible, the app still exists, but the editor is failing to load it—often showing “Untitled” apps with 404 errors.

This can be caused by UI bugs, environment mismatch, or caching issues.

Try opening the app from the Apps list or Solutions, switching environments, clearing cache, or using a direct edit URL.

If the issue persists, it’s likely a platform issue and should be raised with Microsoft support.

Was this reply helpful? Yes No