Skip to Content
We are live but in Staging 🎉
WorkflowsWorkflow 2: Run, Observe, and Retrieve Results

Workflow 2: Run, Observe, and Retrieve Results

Last validated: 2026-05-14

Goal

Execute a published script, watch progress, and retrieve complete outputs including large payloads.

When To Use

  • Scheduled production runs
  • Manual operation/testing against known version
  • Large-output workflows requiring streaming retrieval

A) CLI Path (Unified Plugin)

# 1) Run and watch in one command dodil scriptum thread run invoice-parser \ --version 3 \ --input @./prod/invoice_42.json \ --env \ --result # 2) Save full output and step files dodil scriptum thread result thr_abc123 --save ./out/thr_abc123 # 3) Inspect step details dodil scriptum thread steps thr_abc123 --detail

Argument guidance:

  • --version 0 uses active version; explicit version pinning improves reproducibility.
  • --save creates output.json, summary.json, and step files.
  • thread run attempts streaming watch first, then polling fallback.

B) gRPC Path (Direct API)

# Create thread grpcurl \ -H "authorization: Bearer $DODIL_TOKEN" \ -H "x-organization-id: $SCRIPTUM_ORG_ID" \ -d '{ "script_name":"invoice-parser", "version":3, "input_json":"{\"invoice_id\":\"INV-42\"}", "load_env":true }' \ rpc.dev.dodil.io:443 dodil.scriptum.v1.ScriptumService/CreateThread # Watch thread stream grpcurl \ -H "authorization: Bearer $DODIL_TOKEN" \ -H "x-organization-id: $SCRIPTUM_ORG_ID" \ -d '{"thread_id":"thr_abc123"}' \ rpc.dev.dodil.io:443 dodil.scriptum.v1.ScriptumService/WatchThread # Fetch unary result grpcurl \ -H "authorization: Bearer $DODIL_TOKEN" \ -H "x-organization-id: $SCRIPTUM_ORG_ID" \ -d '{"thread_id":"thr_abc123"}' \ rpc.dev.dodil.io:443 dodil.scriptum.v1.ScriptumService/GetThreadResult # If output_truncated=true, stream output chunks grpcurl \ -H "authorization: Bearer $DODIL_TOKEN" \ -H "x-organization-id: $SCRIPTUM_ORG_ID" \ -d '{"thread_id":"thr_abc123","max_chunk_bytes":1048576}' \ rpc.dev.dodil.io:443 dodil.scriptum.v1.ScriptumService/StreamThreadResult

C) HTTP Path

Management probes

curl -sS https://api.dev.dodil.io:443/health curl -sS https://api.dev.dodil.io:443/metrics | head

Business API via gateway (if deployed)

curl -sS "https://api.dev.dodil.io:443/v1/scriptum/threads/thr_abc123/result" \ -H "Authorization: Bearer $DODIL_TOKEN" \ -H "x-organization-id: $SCRIPTUM_ORG_ID"

Validation Checklist

  1. Thread reaches completed status.
  2. GetThreadResult output is present and parseable JSON.
  3. If output_truncated=true, streamed output reconstruction is successful.
  4. Step inspection confirms expected critical path completion.