Job Schedule
Refer to this document for schedule
SFCC Staging Jobs & Replications
Job fail
There are several reasons which will cause the job to fail.
1. invalid characters
Invalid character such as emoji and non printing character in the product name, description or any other fields may cause the job to fail. We have documented the PIM product upload process in the below confluence article. Please look into it for more details.
2. Jobs or replication overlap
It will cause the running job to fail when another job is started if it is not yet finish, i.e. when the 4-1 differential job is running, it will fail when the 4-2 differential job is started. The running job will also fail when the replication is triggered. Therefore we should avoid doing any replication when the job is running.
These was cause by the catalog was already locked by one of the job/replication so the resources of the current running job cannot be locked which cause the job to fail.
3. invalid .xml
The job will fail when there is an incomplete .xml in the import. An incomplete .xml is caused by the previous job failed or aborted, therefore the xml. file running will become invalid and it will stay in the next job which cause the job to fail again.
There will be an email to notify us when a job is failed. We can find this in the Digital.Support mailbox. So when a job is failed, we can follow the below steps.
Full-import job failed due to invalid characters
eWave has a notification when the full-import job is failed due to invalid character. We can follow the below steps to check the cause of error.
Login to Staging → Go to “Administration > Job”
Go to the failed Job “Akeneo-Full-Import”
Go to “Schedule and History”, download the log file.
Check job log and search where validation is broken
Then Go to “Administration > Development setup”
Go to “Import/Export > src > akeneo > catalog”, check the .xml from the job log screenshot
open it and see on which line is the error:
download the file by clicking the icon before the file
Open the XML and check which product is the line with the error
Go to PIM and remove the invalid characters.
Let the next job runs as schedule.
Raise it to eWave when the job is still fail
Job fail due to other reasons
As mentioned, the job may fail due to jobs or replications overlap or invalid .xml. So when we recieve a notification in Digital.Support mailbox which says the job is failed, we can follow the below handling processes.
Login to Staging → Go to “Administration > Job”
Go to the failed Job (e.g. 4-3-Akeneo-Differential-Import)
If the job failed at the first time from it started, it will retry to run it again on the fail step. So we can just wait and see if it retry success or not. There is total 3 attempts when the step is failed and if the job failed on all 3 attempts, the whole job will failed. Then we to look into the following steps.
Go to “Schedule and History”
Expand the job steps and check which step failed.
Check the possible failed reasons.
During this step, we have to see the timing if it is overlapped with the next job or the manual replication. If yes, we just have to monitor if the next job is success.
When it is not about the overlap issue, we need to monitor if the next job success or fail or not.
- If it is success, we can leave it.
- If it is fail, we need to raise it to eWave.