> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# History and Rollback in StagingPro for BigCommerce
History and Rollback is the StagingPro audit surface and the recovery mechanism. Every data migration and theme deployment lands here with full provenance: who initiated it, what entities were touched, when it ran, where data went, and the result. From the same screen you can roll a botched change back to the previous state with one click.
## Three tabs
When you open History and Rollback, three tabs appear:
| Tab | What it tracks |
| ----------------------- | ------------------------------------------------------------------- |
| **Data Migrations** | All bulk and selective content migrations |
| **Code Deployment** | Theme deployments from the connected GitHub or Bitbucket repository |
| **Scheduled Migration** | Pending migrations queued for future execution (Premium feature) |
## Data Migrations tab
The Data Migrations tab lists every migration with its source environment, destination environment, start and end timestamps, and current status.
### Filtering
Filter controls at the top of the tab:
* **From**, start date for the date range filter.
* **To**, end date for the date range filter.
* **Batch ID**, search for a specific migration by its unique Request ID.
* **Apply Filter** to apply, **Reset** to clear.
### Reading a migration row
Each row shows:
| Column | Meaning |
| --------------------------- | ----------------------------------------------------------------------------------------------------------- |
| **Request ID** | Unique identifier (e.g. `20FDC58D-CC9D-4586-956B-B8AECC5B2C0C`). Quote this to support if logging a ticket. |
| **Source Environment** | Where the data came from |
| **Destination Environment** | Where the data went |
| **Started at** | Migration start timestamp |
| **Status** | Current state (see status meanings below) |
| **Completed at** | Migration end timestamp |
Status meanings:
| Status | Meaning |
| --------------------- | ----------------------------------------------------------- |
| **Publish Completed** | Migration finished and data is published to the destination |
| **Completed** | Processing finished |
| **In Progress** | Currently running |
| **Pending** | Queued, not yet started |
| **Failed** | An error occurred, click into details |
| **Cancelled** | Manually stopped before completion |
### Drilling into per-entity detail
Click the Request ID or **View Details** to expand the migration:
The expanded view lists each entity (e.g. Page Templates, Products, Categories) with:
| Column | Meaning |
| --------------- | --------------------------------------- |
| **Entity** | Type of data migrated |
| **Source** | Source environment for this entity |
| **Destination** | Destination environment for this entity |
| **Status** | Per-entity status indicator |
| **Errors** | Error details if any issues occurred |
Green dot with "No errors" confirms a clean migration. For large migrations you can drill down further into individual item-by-item status with their UUIDs, timestamps, and per-item View Details links.
## Code Deployment tab
The Code Deployment tab tracks theme deployments from the connected repository:
Each row:
| Column | Meaning |
| --------------------------------- | ------------------------------------- |
| **Git ID / Revision ID** | Reference to the code commit |
| **Commit date time** | When the code was committed |
| **Branch Name / Environment URL** | Which branch and where it deployed |
| **Channel ID** | The BigCommerce channel targeted |
| **Approval status** | Whether the deployment was approved |
| **Status** | Deployment state |
| **Design Release Version** | Theme version number |
| **Action** | Deploy, View Logs, Rollback, Schedule |
### Approval workflow
Code deployments may require approval before going live:
* **Pending Approval**, deployment is waiting for review.
* **Approved**, deployment will proceed.
* **Rejected**, deployment will not run.
Available actions depending on state:
* **Deploy**, push the theme to the target environment.
* **View Logs**, inspect detailed deployment logs.
* **Rollback**, revert to a previous theme version.
* **Schedule**, set a future deployment time.
Deployments may take 15 to 20 minutes after approval, depending on theme size. The bottleneck is BigCommerce assembling the theme bundle and accepting the upload, not StagingPro itself.
## Scheduled Migration tab
The Scheduled Migration tab lists migrations scheduled for future execution. This is a Premium-tier feature.
Each scheduled entry shows:
| Column | Meaning |
| --------------------------- | --------------------------------- |
| **Request ID** | Unique identifier |
| **Content Type** | Entity scheduled |
| **Source Environment** | Where data will come from |
| **Destination Environment** | Where data will go |
| **Created at** | When the schedule was created |
| **Scheduled at** | When the migration will run |
| **Completed at** | When it finished, if already run |
| **Status** | Current state |
| **Action** | Cancel button while still pending |
To cancel a scheduled migration:
1. Open the **Scheduled Migration** tab.
2. Find the migration in the grid.
3. Click **Cancel** in the Action column.
4. Confirm.
You can only cancel migrations that have not yet started.
## Audit trail summary
The History and Rollback section gives you a complete audit trail:
* **Who**, the system records which account initiated the action.
* **What**, exactly which entities were migrated.
* **When**, precise timestamps for every activity.
* **Where**, source and destination environments.
* **Result**, success, partial, or failure with error details.
Useful for: compliance reporting, post-incident review, change management, team coordination, troubleshooting handoffs to support.
## Theme rollback
The Action column on Code Deployment offers Rollback. Click it, and StagingPro redeploys the previous theme version to the same environment.
Indicative time: 15 to 20 minutes for the rollback bundle to land on BigCommerce. Useful when a theme deploy regressed checkout or broke a key page.
## Best practices
| Practice | Why |
| ------------------------------------------------------- | ---------------------------------------------------- |
| Check the History tab after every migration | Catch failures while they are still fresh |
| Review failed items promptly | Some failures are transient, others need real fixing |
| Reference Request IDs in team comms and support tickets | Speeds up triage |
| Document any manual interventions | Non-StagingPro changes break the audit trail |
| Don't rename auto-generated branches | Required for commit tracking |
### Before contacting support
To help our team resolve your issue quickly, please gather the following information before contacting the helpdesk:
* Request ID of the problematic migration.
* Started at and Completed at timestamps.
* Error messages from the per-entity view.
* Source and destination environments.