Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

<@U04S8PLJWMT>: ERROR: type "job_status" already exists

The error `ERROR: type "job_status" already exists` is a PostgreSQL schema migration error that occurs in Airbyte when the database migration tries to create a type that already exists in the database. This is similar to other migration conflicts reported in Airbyte.
Based on the knowledge sources, a comparable issue was reported with `abctl` where the migration failed because a type (`source_type`) already existed: [<https://github.com/airbytehq/airbyte/issues/58864|abctl migration error>]
> `ERROR: type "source_type" already exists`
This type of error typically happens when:
• *Upgrading Airbyte* to a new version where the migration script attempts to re-create a type that was already created in a previous run or partial migration.
• *Re-running migrations* on a database that already has partial schema changes applied.
The knowledge sources do not contain enough information to provide a specific fix for the `job_status` type conflict. However, based on the pattern seen in similar issues (like the `pk_connector_rollout` duplicate key error [<https://github.com/airbytehq/airbyte/issues/65134|GitHub issue>] and the `source_type` already exists error [<https://github.com/airbytehq/airbyte/issues/58864|abctl migration error>]), I would recommend:
1. *Check the Airbyte GitHub issues* for your specific version to see if this is a known bug.
2. *Open a new GitHub issue* at <https://github.com/airbytehq/airbyte/issues> with your Helm chart/platform version and full error logs.
I'm sorry, but the knowledge sources do not contain enough detail to provide a definitive resolution step for this specific error. :thumbsup: 0 button :thumbsdown: 0 button :information_source: *Tip:* Mention *@kapa.ai* in the thread for follow-ups or *DM the app* for *1-to-1* help.