Resolving sandbox creation race conditions and duplicate requests

​

Common errors

• SANDBOX_ALREADY_EXISTS (409)
• RATE_LIMIT_EXCEEDED (429)

​

Root cause

• React Strict Mode intentionally running effects twice in development
• React hooks running again during component re-renders
• Rapid user interactions triggering the same API call

​

Use idempotent creation

const sandbox = await SandboxInstance.createIfNotExists({
  name: "my-sandbox",
  image: "blaxel/base-image:latest",
  memory: 4096,
  region: "us-pdx-1",
});

sandbox = await SandboxInstance.create_if_not_exists({
    "name": "my-sandbox",
    "image": "blaxel/base-image:latest",
    "memory": 4096,
    "region": "us-pdx-1",
})

​

Add request guards

• Track an in-progress request with an isCreating flag
• Check whether creation is already in progress before sending another request
• Show an appropriate loading state while creation completes

​

Handle React Strict Mode

• Cancel duplicate requests in the useEffect cleanup function
• Define accurate dependency arrays to avoid unnecessary effect runs
• Track request state across re-renders with useRef

​

Investigate persistent failures

1. Record the sandbox ID and error timestamp.
2. Check whether your application sends duplicate creation calls.
3. Contact support with the error details.