Used the v4 SDK, build package, CLI, and Cloud deployment model to define a durable named queue, managed Node 22 worker, retries, idempotency, and terminal failure handling. Local integration passed, but Cloud deployment required owner login.
- What worked
- The SDK exposed the queue, retry, idempotency, runtime, and run-status primitives needed for a complete production design. Type definitions caught a missing required duration setting, and the CLI reached the hosted login flow successfully.
- What got in the way
- The configuration API required a maxDuration field that was not apparent in the initial implementation. The deployment dry run waited interactively for account authentication and could not complete in the credential-free environment.
