Deployment History & Rollback

Every deployment is automatically logged. Roll back to any previous version in one click.

Deployment history and rollback are available on all paid plans. You must have an active license to access these features.

On this page

  1. How It Works
  2. Viewing Deployment History
  3. Rolling Back a Deployment
  4. History Retention by Plan

How It Works

Every time FetchPress deploys a theme or plugin — whether triggered by a git push or manually — it records a deployment entry containing:

  • The date and time of the deployment
  • The theme or plugin that was deployed
  • The version before and after the deployment
  • The trigger type (push webhook or manual)
  • The deployment status (success, failed, or pending)
  • An error message if the deployment failed

Before each deployment, FetchPress saves a copy of the current code as an artifact. This artifact is what makes rollbacks possible.

Viewing Deployment History

  1. In the WordPress admin, click Deployment History in the FetchPress navigation menu.

  2. The history table shows all deployments within your plan's retention window. You can filter the list by theme/plugin type and by a specific identifier to narrow down results.

  3. Each row displays the deployment date, the item deployed, the version change, the status, and the trigger. Failed deployments show an error indicator — hover over it to see the error message.

If you're on the free plan, the Deployment History page will show an upgrade prompt instead of the history table.

Rolling Back a Deployment

  1. In the Deployment History table, find a successful deployment you want to restore. Only deployments with a Success status can be rolled back.

  2. Click the Rollback button on that row. A confirmation dialog will appear — confirm to proceed.

  3. FetchPress will restore the previously saved artifact for that deployment. If the plugin was active at the time, it will be deactivated during the rollback and reactivated afterward automatically.

  4. The rollback itself is recorded as a new entry in your deployment history with a rollback trigger type, so you always have a complete audit trail.

History Retention by Plan

How long deployment history is kept depends on your subscription tier:

Starter7 days of deployment history retained.
Pro30 days of deployment history retained.
AgencyUnlimited deployment history — no records are ever deleted.

FetchPress runs a daily cleanup job that automatically removes deployment records and saved artifacts older than your plan's retention limit.

Account Management →