BluepointATM Website Restore Recovery — 2026-04-05
Overview
During a routine touch base on the LaMarie project, Melissa flagged an unplanned website restore performed by Mark (E-Shock) on the BluepointATM site. The restore reverted the site to an older version, resulting in data loss and broken form logic. Recovery and re-testing were assigned to Isahaque as a priority task before his upcoming holiday.
This incident was surfaced in the [1] meeting.
Incident Summary
| Field | Detail |
|---|---|
| Discovered by | Melissa Cusumano |
| Caused by | Mark (E-Shock) performed a site restore |
| Reported by client | Raphael (noted missing blog posts) |
| Date of restore | ~2026-04-04 (day prior to this meeting) |
| Assigned to | Isahaque Mahmud |
Impact
- Blog posts lost — Raphael flagged that blog content was missing after the restore.
- Form logic broken — The restore reverted custom form configurations, including page-source tracking logic that had been previously implemented (e.g., "how did you find us" field placement relative to organization fields).
- Client-facing changes lost — Melissa had made live edits during a client call the day prior; those changes were wiped by the restore.
- Scope of loss unclear — Full extent of reverted changes was not yet determined at time of meeting.
Key Decisions
- All forms on the BluepointATM site must be re-tested to confirm they are capturing data correctly and tracking the correct source pages.
- Isahaque will work through the outstanding BluepointATM tasks in ClickUp and complete them before his holiday.
- Melissa will add additional edit tasks to ClickUp (e.g., removing Blog from navigation, moving it to the footer).
Action Items
| Owner | Task | Status |
|---|---|---|
| Isahaque | Re-test all BluepointATM forms for correct data capture and page-source logic | 🔴 Open |
| Isahaque | Complete all BluepointATM ClickUp tasks before holiday | 🔴 Open |
| Melissa | Add remaining Bluepoint edit tasks to ClickUp (e.g., blog nav/footer change) | 🔴 Open |
Context & Notes
- The restore was performed by Mark at E-Shock. The reason for the restore was not communicated to the Asymmetric team in advance.
- This is a recurring risk when external parties (e.g., hosting/maintenance vendors) have restore access without coordinating with the development team.
- Consider establishing a protocol with E-Shock requiring prior notification before any restore is performed on client sites.
Related
- [2]
- [1]