Troubleshooting Stalled WordPress Export and Erasure Requests
What should a WordPress site do when a personal-data export or erasure request is stalled or incomplete?
First identify where the request stopped: confirmation, administrator processing, export notification or erasure review. Preserve the existing request record, inspect the intended recipients and export subject where relevant, and investigate delivery through the site’s approved mail process. If erasure reports retained information, document the exact result and assign it for appropriate review instead of declaring the request complete.
Locate the stage where the request stopped
WooCommerce describes a WordPress erasure page that can send a confirmation request to the customer’s email or via their username. Determine whether the request is waiting for confirmation, administrator processing, an export notification or an erasure-result review. Preserve the current record and log the last verified action instead of creating duplicate requests or repeating irreversible actions.
Sources: Right to Erasure Requests for GDPR with WooCommerce.
LifterLMS states that a site administrator processes a request once it is confirmed. When confirmation is complete, assign processing to a named operator and record the hand-off; otherwise investigate the confirmation path first.
Sources: Handling User Data Export and Erasure Requests | LifterLMS.
- Identify whether confirmation is outstanding.
- Identify whether administrator processing is outstanding.
- Preserve the existing request record while investigating.
Check the confirmation-notification recipient
WordPress documents a filter for the recipient of the data-request confirmation notification. Ask a developer or site maintainer to inspect the intended recipient when confirmation appears misrouted, and record the expected recipient and observed outcome. Do not treat the presence of a recipient filter as evidence that the notification was delivered.
Sources: Privacy Related Options, Hooks and Capabilities – Plugin Handbook | Developer.WordPress.org.
- Check the intended confirmation recipient.
- Treat routing controls as diagnostics, not delivery proof.
- Use the approved mail process for delivery investigation.
Inspect export email subject and recipient controls
WordPress documents a filter for the recipient of the personal-data export email notification. For an export-routing issue, record the intended recipient, observed recipient or absence of a message, and the person responsible for investigation.
Sources: Privacy Related Options, Hooks and Capabilities – Plugin Handbook | Developer.WordPress.org.
WordPress documents a filter for the subject of the email sent when a personal-data export request is completed. Use the expected subject as a diagnostic field alongside the recipient and outcome, then follow the approved operational process to investigate delivery.
Sources: Privacy Related Options, Hooks and Capabilities – Plugin Handbook | Developer.WordPress.org.
- Check the intended export recipient.
- Check the expected completed-export subject.
- Record the observed outcome and investigation owner.
Escalate retained-data exceptions before closure
WooCommerce says that information a plugin needs to retain is displayed at the end of the erasure process. Record the exact displayed outcome, responsible plugin, reviewer and next action, then escalate the exception rather than declaring the request fully erased. A plugin message does not establish whether retention is legally justified or whether further deletion is appropriate.
Sources: Right to Erasure Requests for GDPR with WooCommerce.
- Capture the exact retained-data message.
- Name the component that reported it.
- Assign an appropriate reviewer before closure.
Use a clear hold, retry and closure record
Keep one resolution record showing the request’s current status, last verified action, evidence reviewed, next owner and closure or hold decision. Use a hold state for unresolved confirmation, routing or retained-data questions, and assign a bounded next action instead of retrying without a diagnosis. Confirm current provider prerequisites before repeating an irreversible or service-affecting action, and distinguish technical completion from any legal assessment.
- Keep one record for one request.
- Record status, last verified action, evidence, next owner and decision.
- Use a hold state for unresolved routing or retention questions.
Request exception triage card
Use this triage card when a WordPress personal-data request cannot be closed normally. It identifies the current stage, captures the observed outcome and assigns a bounded next action.
| Stage | What to verify | Record now | Next owner |
|---|---|---|---|
| Confirmation | Whether confirmation is outstanding and who should receive the notification. | Status; last verified action; expected recipient; observed outcome. | Site maintainer or assigned operator. |
| Administrator processing | Whether confirmation is complete and processing remains outstanding. | Status; last verified action; processing evidence. | Assigned administrator. |
| Export notification | Expected recipient and completed-export subject against the observed result. | Recipient; subject; delivery evidence; observed outcome. | Site maintainer. |
| Erasure exception | Exact retained-data outcome and reporting component. | Displayed result; component; evidence; review status. | Appropriate operational or legal reviewer. |
| Closure or hold | Whether every exception has an owner and decision. | Current status; closure or hold decision; next action. | Request owner. |
The card supports operational hand-off. It does not prove email delivery or decide whether retained information may legally remain.
Related guidance
What follow-up questions matter most?
- Where should I start with a stalled request?
- Identify whether the request is awaiting confirmation, administrator processing, an export notification or erasure-result review. Preserve the existing record and avoid creating duplicate uncontrolled actions while investigating its current state.
- What can I inspect for a missing confirmation?
- WordPress documents a filter for the confirmation-notification recipient. A developer or maintainer can inspect the intended routing, but the control does not prove that a message was delivered.
- Can I close a request with retained data?
- Document the exact plugin result, responsible component, reviewer and next action. Keep the request open or formally held until the exception has an assigned decision.
What steps does this workflow follow?
Triage a stalled WordPress personal-data request
- Locate the current stage: Determine whether confirmation, administrator processing, export notification or erasure review is outstanding.
- Preserve the request state: Keep the existing request record and record the last verified action rather than repeatedly creating or processing requests.
- Inspect routing controls: Ask an appropriate maintainer to inspect the intended confirmation and export-notification controls, then investigate delivery through the approved mail process.
- Escalate retained results: Record the exact displayed retention outcome and assign it to the appropriate operational or legal reviewer.
- Close or hold clearly: Record the current status, last verified action, evidence reviewed, next owner and closure or hold decision.