> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useshipd.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Publish a snapshot

> Retry publication when a saved flag change has not reached your application.

## Overview

Flag changes publish automatically after `shipd push` or a dashboard save. If publication failed, you can manually publish the environment's current configuration again. This does not change flag definitions or bypass approvals.

## Before you publish

Follow [Troubleshooting](/resources/troubleshooting) first: confirm the project, environment, SDK key, and approval status. A pending approval must be approved before its change can reach SDKs.

You need the `snapshot.publish` permission, available to editors, admins, and owners. Authenticate with `shipd login` or a service account token with that scope and access to the target environment.

## Retry publication

```bash Terminal theme={null}
shipd snapshots publish --project web-app --env production
```

After the command succeeds, allow the SDK to refresh and check the flag again. A client with polling disabled needs an update notification or a manual refresh.

If publication fails again or the value is still stale, contact [support](mailto:hey@useshipd.com) with the project, environment, error, and request ID if available. Do not send credentials.

For publication status and additional recovery commands, see the [CLI reference](/reference/cli#shipd-snapshots-outbox).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.