Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/content/docs/Patchstack App/Pulse/pulse-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -86,13 +86,13 @@ That happens more often than you might expect. Patchstack's re-fetch reads the H

Beside those timestamps, a Pulse site's header carries a **deploy status**. Building and deploying are separate events, and Patchstack tracks them separately.

Connect's `mark-build` step stamps each build's fingerprint into the HTML it publishes. Patchstack reads that fingerprint back off the live site — from the widget when a visitor loads a page, and from its own scheduled fetch of the published page — and compares it against the builds you have reported. That comparison is what the status says out loud:
Connect's `mark-build` step stamps each build's fingerprint into the HTML it publishes. Patchstack reads that fingerprint back off the live site — from the widget when a visitor loads a page, and from its own scheduled fetch of the published page — and compares it against the builds you have reported. A preview of the app runs the same build, so a check-in from one is not counted as the live site: a builder's editor preview (Lovable, Bolt, Replit) or a host's deploy preview (Netlify). When the address Patchstack has on file is a preview, it moves to the published address the first time the widget sees a scanned build there, or when a build reports the published address (set `url` in `.patchstackrc.json`). Patchstack's scheduled check reads only the address on file, so on a site with few visitors, setting `url` is what lets the deploy be confirmed. That comparison is what the status says out loud:

| Status | What it means |
|--------|---------------|
| **Deployed \<when\>** | The build serving traffic is the one Patchstack scanned. |
| **Last build \<when\>** | The same, except nobody has seen this app change build since Patchstack started watching. The time shown is when the build ran, not when it went live. |
| **Deploy reported** | A production build reported itself, but the live page has not been seen running it — either the page was read since and is not running it, or the label was assumed from the project's builder. Publish if you have not, or open the published site once so the widget can confirm the build. |
| **Deploy reported** | A production build reported itself, but the live page has not been seen running it — either the page was read since and is not running it, or the label was assumed from the project's builder. Publish if you have not, or open the published site once so the widget can confirm the build. Opening the app's preview does not count. |
| **Needs deploying** | A newer build was scanned, but the live site is still serving an older one. Deploy to put it live. |
| **Deployed without Patchstack** | The live site is running a build Patchstack never scanned — the build ran without Connect. Run the build again with `@patchstack/connect` so its packages get checked. |
| **Live, build unverified** | The widget is checking in from the site's address, but the page carries no build marker, so nothing can say which build is live. Typically a build made on a developer's machine and uploaded by hand. Build with `PATCHSTACK_ENVIRONMENT=production`, or run `mark-build --production` before uploading. |
Expand Down