UC-19: Code Runtimes and Code-Run Execution
Role-gated control-plane steps are intentionally excluded from this public guide; use support escalation when those operations are required. Shared company context: Gharart.com Company Context Need operator help? Escalate through Troubleshooting and Support with request IDs and repro artifacts.
Developer Outcome
Ship code runtimes, Smartwork/OpenAnalyst launch handoff, and code-run execution for Gharart.com with reproducible API steps, operational limits, and clear debugging playbooks.
Prerequisites
- A valid handle and environment access for Gharart.com.
- JWT and/or PAT credentials with required scope for this use case.
- When using the desktop runtime, access to the Smartwork/OpenAnalyst browser pairing flow.
- Access to logs, support escalation endpoints, and test workspace.
Gharart Scenario
Automated creative QA jobs in isolated runtime.
Persona: Automation platform lead
Business goal: Register secure runtime images and execute controlled code-runs for campaign QA automation.
Step-by-Step Flow (UI + API)
- Open the relevant Gharart workflow in the dashboard and confirm actor role access.
- Execute route calls in sequence for this use case and capture response IDs. When execution starts from Smartwork/OpenAnalyst, begin with
GET /v2/account/openanalyst/meto confirm the browser session and entitlement context. If you need a local runtime, complete browser pairing first, then continue into/v2/account/openanalyst/launchbefore moving into handle-scoped runtime actions. - Validate expected state in UI and API after each step before moving forward.
- Record artifacts (request ID, run ID, deployment ID, slug, or token) for support handoff.
Primary API Routes
| Method | Path |
|---|---|
| GET | /v2/account/openanalyst/me |
| GET | /v2/handles/{handle}/code-runs/{runId} |
| GET | /v2/handles/{handle}/code-runs/{runId}/output |
| GET | /v2/handles/{handle}/code-runtimes |
| GET | /v2/handles/{handle}/code-runtimes/{runtimeKey} |
| POST | /oauth/openanalyst/desktop/start |
| POST | /v2/account/openanalyst/launch |
| POST | /v2/handles/{handle}/code-runs |
| POST | /v2/handles/{handle}/code-runs/{runId}/cancel |
| POST | /v2/handles/{handle}/code-runtimes/{runtimeKey}/validate-image |
| PUT | /v2/handles/{handle}/code-runtimes/{runtimeKey} |
Limits and Quotas
- Respect per-route throttles and daily write limits before bulk operations.
- Use idempotency-safe retries for write endpoints to avoid duplicate business actions.
- Schedule high-volume workflows outside peak campaign windows where possible.
Where This Breaks
- validate-image returns failed due digest mismatch
- run submission blocked by active run capacity limit
- output retrieval missing because run finalized with error
How Gharart Debugs It
- Re-validate runtime image uri and digest pair
- Check active run count before submitting new run
- Inspect run status transitions before fetching output
Escalation
Use end-user escalation path:
- Submit
POST /v2/support/report. - Include
summary,details, and when availablehandle,sessionId,requestId,reproArtifact.
Audience boundaries:
POST /v2/operator/escalationsis an internal operator workflow and not an end-user escalation action.POST /v2/public/content-reportis for public abuse moderation reports, not product incident escalation.