Skip to main content
The Change Logs tab is the activity audit surface for RollbackPro. Two sub-tabs split the view: Change Logs for restore-activity audit, and Webhook Logs for the raw BigCommerce API event stream. Use this tab when you need to understand what RollbackPro did, when, and whether it succeeded. Change Logs main view

​
Section title and navigation

The header area shows the RollbackPro app name, a brief overview of the section, and the navigation tabs (Dashboard, Restore Center, Change Logs, Settings). Two sub-tabs:
  • Change Logs, data grid of restore activity statuses.
  • Webhook Logs, data grid of API responses received from BigCommerce.

​
Search and refresh controls

Search and refresh controls A search box at the top filters the grid. The text you enter is searched across the ID, Event, and Status columns. The refresh button reloads the visible grid.

​
Change Logs sub-tab

Change Logs sub-tab grid The grid columns:
ColumnWhat it shows
IDUnique change-log identifier
EventDescription of the event (e.g. “Restore Product 12345 to version 17”)
StatusSuccess or Failure
Date and TimeTimestamp of the entry
View buttonAppears only on Failure rows
Clicking the View button on a Failure row opens a popup explaining the failure and asking whether to escalate to Vortex IQ support: Failure popup with escalate option
“We encountered an issue while processing your request due to a data mapping error with the BigCommerce API. Would you like our support team to investigate this and get back to you?”
Click Yes and an email is sent to helpdesk@vortexiq.ai for troubleshooting: Confirmation that escalation was sent

​
Webhook Logs sub-tab

Webhook Logs sub-tab grid The grid columns:
ColumnWhat it shows
Log IDUnique webhook log identifier
EntityData entity (Product, Category, Customer, etc.)
EntityIDEntity-level unique identifier
ServiceType of webhook
Error MessageResponse received from the BigCommerce API
Date and TimeTimestamp of the webhook log entry
View buttonOpens the full BigCommerce API response payload
Use the Webhook Logs view when you need to debug why a specific record failed to back up or restore. The full API response often shows the underlying BigCommerce error (rate limit hit, malformed payload, missing dependency).

​
Help button

The Help button in the corner opens the corresponding help article in the knowledge base.

​
When to use Change Logs vs Webhook Logs

QuestionUse which sub-tab
Did my rollback yesterday actually succeed?Change Logs
Why did the rollback fail?Change Logs (View on the Failure row)
Why did this Product not back up after I edited it?Webhook Logs (filter by Entity Product, Service the webhook type)
Did BigCommerce return an unusual error?Webhook Logs

​
FAQs

Q. The Change Logs grid is empty. Most likely cause: no rollback operations have been run yet. Backup activity itself does not appear in Change Logs (those go to Webhook Logs). Run a single-item rollback to populate the Change Logs grid. Q. Webhook Logs show “rate limit exceeded” errors. Should I worry? RollbackPro automatically retries on rate-limit errors with exponential backoff, so transient hits are recovered without data loss. Persistent rate-limit issues over many minutes warrant a support ticket. Q. I clicked “Yes” to escalate a failure but I have not heard back. Escalation creates an email ticket with the helpdesk team. Response time depends on your support SLA tier. Confirm receipt at https://helpdesk.vortexiq.ai/portal/en/home where you can track all your tickets. Q. Can I export the Change Logs? Not currently from the UI. The data is retained per the backup retention policy of your subscription; for export support reach out to the helpdesk.