DocumentationWorkspace
Store Statuses
Read the status badge on a workspace store card without assuming more than it confirms.
What this covers: You will understand whether a store has a successful published version or is currently publishing.
The badge on each store card is a quick workspace summary. It is not a complete history of every publish attempt, so open the project when you need to verify the latest change.
Entry path: Workspace sidebar → Stores → store card status badge.
Status meanings
| Badge | What it confirms | Safe next step |
|---|---|---|
| Drafted | Runner does not have a successful published version to show for this card, and publishing is not currently in progress. | Open the store and review its conversation, preview, and publishing controls. |
| Deploying | The latest publish operation is still in progress. | Wait, then check the card and task details again. Do not start repeated publish attempts. |
| Published | The store has at least one successful published version and is not currently showing an in-progress publish. | Open the live view or project details to confirm whether the latest intended change is present. |
Published does not guarantee that the most recent attempt succeeded; it confirms that a successful published version exists. Drafted does not necessarily mean nobody ever tried to publish. A failed attempt does not receive its own workspace-card label in the current interface.
Verify a recent change
- Read the badge on the workspace Stores page.
- Select the store preview image or name.
- Open the conversation that requested the change.
- Review its task state and Details.
- Check Preview or Storefront.
- If the store is Published, compare the live result with the intended change before sharing it.
If the badge seems wrong
- Reload the workspace Stores page once after an in-progress publish has had time to settle.
- Open the project and read the most recent publish or task message.
- Use Details to distinguish a completed Runner task from a completed publish action.
- Do not infer that a failed change is live only because an older version remains Published.
- If no successful version exists, continue work in the preview before trying to publish again.