@kapa.ai got this also WARN Failed to update workload status to launched. Workload may be reprocessed on restart.Exception: io.airbyte.workload.api.client.generated.infrastructure.ClientException: Client error : 410 Gone {"message":"Trying to set a workload in a terminal state (success) to launched"} message: Client error : 410 Gone {"message":"Trying to set a workload in a terminal state (success) to launched"} stackTrace: [Ljava.lang.StackTraceElement;@5db4ae72

The error message you are seeing:

Client error : 410 Gone {"message":"Trying to set a workload in a terminal state (success) to launched"}

indicates that Airbyte attempted to update the status of a workload to "launched" after it had already reached a terminal state (such as "success"). This is not allowed, and the API returns a 410 Gone error in response. The log message:

WARN Failed to update workload status to launched. Workload may be reprocessed on restart.

means that the system tried to transition the workload's state incorrectly, possibly due to a race condition or a retry after the job had already completed. This can result in the workload being reprocessed if the system restarts, but it does not necessarily indicate a critical failure—more a state management issue. This behavior is confirmed in the logs from similar issues, where the same 410 Gone error appears when trying to update the status of a workload that is already in a terminal state. The stack trace and error message are consistent with this scenario, and it is not uncommon to see this warning if there are retries or delayed status updates in the Airbyte platform's workload management system. The workload itself has already finished, so this warning can generally be considered informational unless you are seeing jobs being incorrectly retried or stuck as a result of this state mismatch. If you are experiencing repeated job hangs or retries, further investigation into the workload lifecycle and job orchestration may be needed, as seen in related issues and logs from the platform codebase [source-custom/forked "An unknown error occurred. (HTTP 504)", "Failed to find output files from connector within timeout of 9 minute(s). Is the connector still running?"](https://github.com/airbytehq/airbyte/issues/48600). If you need to prevent this, ensure that your Airbyte deployment and connectors are up to date, and monitor for any jobs that are being retried unexpectedly. If the problem persists, it may be worth opening an issue with detailed logs for further investigation.