Overview

AVFlow emits events for job lifecycle changes. On AVFlow Cloud, configure a webhook in the Console to receive them.

Event types

Event	When
job.starting	Runtime accepted the job; pipeline bootstrapping
job.started	Pipeline active
job.completed	Job finished normally
job.failed	Job failed (e.g. pipeline start error); includes error
job.idle_timeout	Idle policy triggered (reason is source or sink)
job.max_duration_reached	Max duration policy triggered
component.error	A component reported an error (component.name / role / type on the envelope; does not always terminate the job)

Terminal job events include a reason (shutdown, failed, api_stop, source, sink, …) so consumers can tell normal stop apart from policy or fatal errors.

The runtime also emits internal usage.tick events over HTTP. Shared GPU nodes send instance.heartbeat over their authenticated WSS control channel instead. Neither event is delivered to customer webhooks.

Envelope

Each delivery is a JSON POST:

{
  "schema": "avflow.events.v1",
  "eventId": "evt_…",
  "event": "job.started",
  "eventTime": "2026-06-10T12:00:00Z",
  "instance": {
    "id": "instance_…",
    "version": "v1.2.3"
  },
  "appId": "app_…",
  "job": {
    "id": "job_…",
    "name": "my-job"
  }
}

See Webhooks for setup and verification. Use Console Usage for billing details.