Design prototype — proposed request-detail screen. No equivalent was found in the ops portal; today an operator would open Client Requests, then separately navigate to Environments, then Backups, then Logs, to assemble this same picture by hand. ← back to journey
Client Requests  ›  RESTORE-4471
Proposed

wrenfield.example — site not serving after plugin update

RESTORE-4471 · Wrenfield Studio · opened today, 9:42am
Needs action

What the customer told us

What changed: A plugin or theme update
Roughly when: This morning, around 9am AEST
Notes: "We updated a caching plugin this morning and the homepage went blank right after."
Snapshot offered: Yes — customer took a self-service backup of the current (broken) state before sending this.

Backups on cp-40112 Open in Environments →

CreatedSizeStatus
Today, 9:41am (customer, self-service) 121 MB Committed
06/08/2026, 6:52:11pm 28.2 MB Expired
06/08/2026, 6:49:18pm 0 B Failed Expired
This is the actual, live state of this environment's backup history (environment #40114, inspected during this investigation) — every existing backup is either expired or failed, so there is nothing here Sam can restore to. The only usable copy is the customer's own snapshot of the already-broken site. This is exactly the dead end the customer-facing "blocked" state is built for.

Environment

StatusNot serving
OrganisationWrenfield Studio
Groupha-shared-04
Hostnamecp-40112.hosting.example.net
Fileroot/var/www/cp-40112.hosting.example.net

Apache error log Open Logs →

[09:03:12] PHP Fatal error: Uncaught Error: Call to undefined function
wpcache_flush() in /httpdocs/wp-content/plugins/turbo-cache/init.php:44
[09:03:12] AH01071: Got error 'PHP message: Fatal error'
[09:03:12] [core:error] File does not exist: /httpdocs/favicon.ico
[09:03:41] PHP Fatal error: Uncaught Error: Call to undefined function
wpcache_flush() in /httpdocs/wp-content/plugins/turbo-cache/init.php:44
Assumed, not confirmed: that pulling backups, environment status, and logs onto one screen, keyed off a request, is something operators would actually want — it wasn't possible to interview an operator during this investigation. What is confirmed: today these three things live on three separate ops pages (Client Requests, Environments▸Backups, Environments▸Logs) with no link between a request and the environment it concerns.