Lifecycle ownership stays external
The external process owns start, heartbeat, completion, and failure. A durable caller-supplied run ID supports exact retries and process recovery without pretending business side effects are idempotent.
Direct answer
An external automation uses a narrowly scoped project and job credential to start or resume a durable run and report operational signals over HTTPS.
The external process owns start, heartbeat, completion, and failure. A durable caller-supplied run ID supports exact retries and process recovery without pretending business side effects are idempotent.
The current TypeScript instrumentation package is private and internal. Telemetry is bounded and in memory, attachments require careful scrubbing, and delivery reports expose degraded outcomes rather than masking them.
EARLY ACCESS