Launching and running it
Why are my latest changes visible in the preview but not on my live app?
Lumos · Updated
Your preview and live app may be running different versions. Check whether the new changes were published successfully and whether you're opening the URL for the intended environment. A working editor preview doesn't establish what is running publicly.
Start with the latest deployment record. Find its status and, if available, the version or commit it used. If the build failed, the public URL may still be serving an earlier successful version.
Follow the change to the public URL
- Confirm the change was saved in the project or branch used for publishing.
- Check whether publishing requires a separate action or a configured automatic workflow.
- Inspect the latest deployment result and resolve any reported failure.
- Open that deployment's URL, then compare it with your normal public address.
With Prisma's documented deploy-on-push workflow, the default branch deploys production and other branches get preview environments.
If the correct deployment shows your change but the usual address doesn't, investigate the domain's destination and caching. Test in another browser session before clearing stored data. Clearing browser storage could remove information your app keeps locally.
When the difference is in records rather than the interface, check the database too. A preview may use separate data from production. Avoid copying production data into a preview just to make the screens match.
In the Builders Handbook
Get a live URL explains how to check the version you intend to share and repeat those checks after updates.