iCommerce Sandbox Troubleshooting

Distinguish runtime, credential, store, authority, execution-outcome and business-state failures.

Retain sandbox/execution identity, store path, original commerce request key, timestamps and correlation IDs. Inspect the complete structured results before deciding to retry.

Symptom	Inspect
Sandbox 401/403	Sandbox API-key format, verified account, scopes and sandbox roles
CLI/native loader failure	Image, Node version, native architecture/libc and optional dependency installation
No expected records	Absolute database path, mounted storage, workspace and actual returned record IDs
Preview with no business change	Apply setting, policy decision and whether the operation was only a rehearsal
Apply rejected	Trusted policy/principal/store config, capability/delegation, versions, approvals and budgets
HTTP 200/exit zero but incomplete work	Execution outcome, receipt status, per-step findings and current state
Lost command response	Original execution receipt and recovery contract
Local payment exists without provider result	Native ledger and external settlement are separate outcomes
Shipped status but unchanged stock	Explicit physical stock posting
State lost after replacement/termination	Actual durable workspace and cleanup semantics

A later authentication failure or timeout does not establish that an earlier mutation rolled back. Preserve the original key and payload; inspect authoritative receipts and state before an explicit recovery. New keys can produce new effects.

Use write controls, Sandbox quickstart, and Sandbox operations. Provide redacted IDs, errors and timestamps for support, not secret values or complete credential-bearing commands.