BigCommerce: Unexpected Staff Action Logs
Timeline of updates
- resolved
We identified an issue where a subset of stores may see unexpected Staff Action Log entries generated by an API-driven background process. These entries are display-only logging artifacts and do not reflect staff user activity or changes made to the store.
Some entries may continue to appear while we complete remediation. Store functionality, data, and security are not impacted, and no action is required.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
042b911ac094bb7e…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by BigCommerce, started 2026-07-08 05:27 UTC, resolved after 0 min, 1 update(s).
- Title
- Unexpected Staff Action Logs
- Vendor
- BigCommerce
- Date
- URL
- https://rewindex.com/company/bigcommerce/incidents/vghz257rl8qx
BigCommerce profileRecent BigCommerce incidentsAll outages on July 8, 2026BigCommerce in July 2026MarkdownJSON