@kapa.ai can I set a timeout to a workload so if a job is pending it goes on error after this timeoit?

Yes, Airbyte has built-in mechanisms to handle workloads that run too long or remain in a pending/not-started state. Here's what the knowledge sources indicate: Workload Timeout Mechanisms Airbyte's

WorkloadMonitor

automatically checks for several conditions: • Not started workloads: Jobs that haven't started are monitored and can be cancelled. • Not claimed workloads: Workloads that haven't been picked up are checked and cancelled. • Non-heartbeating workloads: Jobs that stop sending heartbeats are cancelled. • Running too long (non-sync): Non-sync workloads have a timeout of 4 hours (

PT4H

). • Running too long (sync): Sync workloads have a timeout of 720 hours (

PT720H

). [sync jobs hanging] Configuring the Sync Job Timeout For older/Docker-based deployments, you can configure the maximum timeout for sync jobs using the environment variable:

SYNC_JOB_MAX_TIMEOUT_DAYS=3

The minimum value for this variable is 1 day. [sync hangs] Important Limitation The knowledge sources do not explicitly describe a way to set a fine-grained timeout (e.g., in hours or minutes) specifically for pending workloads beyond what the

WorkloadMonitor

already handles automatically. The

SYNC_JOB_MAX_TIMEOUT_DAYS

variable controls the overall sync job timeout, but its minimum granularity is 1 day. If you need more granular control, the knowledge sources suggest tweaking job timeout environment variables as referenced in the Airbyte operator configuration docs. [job timeout config] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.