Why does calling UpdateETL fail when a data transformation job is running?

Error message

SDKError: StatusCode: 400 Code: ParameterInvalid Message: Previous operation has not finished, status is RESTARTING{"httpCode":400,"requestId":"6867****************96ED","statusCode":400}

Error description

At a specific time (T1), an update operation was performed by calling the UpdateETL API through the SDK, but the operation failed. When checking the console later (at time T2), the job status showed Running.

Answer

This is normal behavior caused by the time difference between the operation and status check. At time T1, the job was in the restart process and could not accept update operations. By time T2 when you checked the console, the restart process had completed, so the status displayed as normally running. This is not a system display error or API issue but a natural result of the time gap between the SDK operation and console status check. When performing job operations, you should consider the transition time of job status. If the job has just been restarted, you need to wait until the job status is completely stable before executing update operations to obtain more predictable results.