> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/jet-bridge-deployment/logs-and-troubleshooting/published-changes-missing.md).

# Published changes are missing

Use this sequence when a change appears in Preview but the audience sees an older or different app.

## Check the release path

1. Confirm that you are inspecting the intended app and environment.
2. Identify a specific visible change that should be in the release.
3. Open [Version History](/ai-app-builder/test-and-publish/version-history.md) and note the version being previewed.
4. Confirm that the intended changes were published; Previewing now is not a published-version indicator.
5. Open the configured published address, rather than a builder or preview address.
6. Sign in as the intended user and check the same page and action.

The invitation dialog warns that non-builder users see the published app. A builder's successful preview does not establish that a release is available to those users.

## If the result still differs

Check whether the user is following an old bookmark, a different custom domain, or an embedded URL pointing to another app or environment. Compare the exact addresses.

Reload the published page after confirming the release. If only one user sees a difference, check their account, team, and record scope before attributing it to an outdated version.

Capture the version, address, user role, time, and publication result. Use [deployment diagnostics](/jet-bridge-deployment/logs-and-troubleshooting/resource-and-deployment-errors.md) for loading failures and [access troubleshooting](/jet-bridge-deployment/logs-and-troubleshooting/published-app-access-fails.md) for role-specific differences.

After correcting the cause, repeat [release verification](/jet-bridge-deployment/publish-your-app/verify-a-release.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/jet-bridge-deployment/logs-and-troubleshooting/published-changes-missing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.