:wave: we're seeing an increase in `409 Client Err...
# airbyte-apih
Henri
06/16/2023, 6:15 PM👋 we're seeing an increase in
409 Client Error: Conflict for url: <https://api.airbyte.com/v1/jobs>Henri
06/16/2023, 6:21 PMIt looks like the sync was actually kicked off and succeeded in the Airbyte UI.. For some reason we got a 40x back on the first call to
/jobst
Terence Cho (Airbyte)
06/16/2023, 8:30 PMHi Henri, you’re correct, 409's usually means that there is already a sync in progress and that the response body usually contains something like:
Copy code
{
"type": "<https://reference.airbyte.com/reference/errors#try-again-later>",
"title": "try-again-later",
"status": 409,
"detail": "A sync is already running for: 7b4b17fe-7fe6-4349-8f66-5c3d1811115b"
}Terence Cho (Airbyte)
06/16/2023, 8:31 PMWe’ll look into why the first request might have returned an error code even though the request actually worked.
h
Henri
06/20/2023, 1:23 PMPerfect! Thanks for confirming that @Terence Cho (Airbyte), I'll add some logic on our side to account for that.
u
user
06/20/2023, 1:24 PM@Henri created a Task INFR-949 Airbyte <> Dagster: Account for 409 sync in progress
j
Julien DEBLANDER
08/03/2023, 1:57 PMHi @Terence Cho (Airbyte) ,
Would you have any update on that? I'm experiencing the same issue with airbyte jobs triggered by Dagster. All my Airbyte jobs are displayed as failed even though it was correctly triggered.