Update job still busy
When you export a plan from SWB, it is a prerequisite that a previous update job is finished. If previous update job is still busy, a new export of the plan is not allowed.
The plan is exported to the
and the BE update job is triggered using .The BE update job then updates BE based on the
. To avoid two update jobs running at the same time, SWB validates that the previous update job is not running. If the BE update job is not finished, a message is displayed that the update job is still running.You can clear previous update jobs from SWB, but you can only clear your own update jobs.
If your previous update job is stuck, you can clear the update job and restart SWB.
To clear the
, go to then select .Update job still busy occurs more than once
can occur, but this is not the standard situation. If the occurs regularly, you must investigate and fix the cause of the issue. Technically, you can add a in the workflow before accepting the plan, which would clear any potential update job still running, but this will not fix the cause of the issue.
ION API OAuth2 credentials are created for each SWB user. The export is handled on a user level and you must not be linked to the same M3 BE user. If you are using the same ION API Oauth2 credential, you are exporting to the same
. Therefore, you are blocking each other and this causes the situation.The update job duration depends on the number of orders and operations that are exported to the
and number of other jobs that are running on the server. If you are exporting, plan the sequence several times. You must complete the first update job before starting the next update job to avoid the situation.The update job is triggered from SWB, but the update job is running in BE. You must analyze the update job in BE. SWB uses Managing data that is not imported.
to retrieve the status of the update job. To analyze the value received from the API, follow the steps in