We couldn't pull that message back — it's still queued.

Experiment changes, traffic, and results. Exact Runner messages, recovery steps, and checks for the completed result.

Refresh results when they cannot load; the experiment can still be running. A failed stop, cancellation, approval, or traffic change leaves the stated running/queued/traffic state in effect. Inspect that state before repeating the action. Preserve your pending request or edits, and retry only the intended operation.

For a failed launch, no store change occurred as stated. For missing project context, reload the store and try again. Confirm the experiment’s status, traffic share, and applied result after recovery, rather than assuming the error stopped traffic. Escalate with the experiment and request identifiers if the state is unclear.

Messages covered:

• We couldn't pull that message back — it's still queued.
• Your message didn't send — nothing was lost, try again.
• Visitors go back to your current store right away. This test can't be resumed.
• We couldn't put the changes live — your store is unchanged. {message}
• We couldn't find this store — reload the page and try again.
• We couldn't stop it — the experiment is still running. {message}
• We couldn't apply that — traffic is unchanged. {message}
• We couldn't dismiss that — please try again. {message}
• We couldn't change the traffic share — it's unchanged. {message}
• We couldn't load your results right now, but your experiment is still running. Refresh to try again.
• We couldn't start Experiments. Nothing changed on your store — try once more.

For repeated failures, see what to send Runner.