`queued` missing from `JobStatusEnum`, breaking Airflow DAGs on capacity-enforced syncs

[magdagultekin]

Summary

Airbyte Cloud started returning queued as a job status for capacity-enforced syncs, but JobStatusEnum in the SDK does not include it. This causes Airflow DAGs using the Airbyte provider to fail immediately on parse.

Error

AirflowException: 'queued' is not a valid JobStatusEnum

Environment

• airbyte-api 0.53.0
• apache-airflow-providers-airbyte 5.5.0
• Airbyte Cloud, capacity-based plan

Root cause

The OpenAPI spec only includes pending | running | incomplete | failed | succeeded | cancelled. The queued status is described in Cloud docs as valid for capacity-enforced syncs but is absent from the spec, so the SDK raises a validation error when it encounters it.

Impact

Production pipelines are blocked whenever workers are saturated and jobs enter queued state. This is not environment-specific — any customer on a capacity-based plan using the Jobs API or Airflow provider should hit the same failure.

Steps to reproduce

1. Use a capacity-based Airbyte Cloud plan.
2. Trigger enough syncs to saturate workers.
3. Poll job status via the Jobs API or Airflow provider — a job in queued state will cause a parse failure.

Ask

Add queued to JobStatusEnum in the OpenAPI spec and release a patch.