Given the same input, IMan job completes only 1/7 attemptes. (5 replies)
Randy, I wouldn't expect errors.txt to be updated if there are no errors.
What are integrations are running on this?
Support
Agreed, I wouldn't expect errors.txt to be updated if there are no errors, I was simply highlighting the error that we DO receive when the job does not complete successfully.
There are a few other jobs running on that machine, but they never overlap:
There are 8 total jobs:
- 4 of them run once a day in the middle of the night (10:30PM, 12AM, 1AM, 2AM)
- 2 of them running once a day during the day (9AM, 12:30AM)
- 1 runs hourly, but has a difference source (DB vs Excel reader), and shouldn't collide (:08 of the hour)
- The job in question, which runs every 15 minutes, on the hour (:00, :15, :30, :45) and takes less than a minute to run where there are no products to sync (as is the case in my screenshots above)
The job runs from my screenshots where the job silently failed do not overlap with any other jobs running.
Any help, guys?
Hello?
Closed due to inactivity.
One of our clients has a spreadsheet sync job which reads CSV files, and inserts/creates products in Magento.
They are having a weird issue, where this IMan job will only complete 1/7 runs, despite the fact that it is processing the exact same data. The step where IMan seems to get stuck is on one of the last steps of the job where we write an Excel file with any processed data. In the cases I'm seeing, there is no data being processed because there are no spreadsheets in the source directory. Even so, this job still only finishes 1/7 times, or about once every 2 hours, as it runs every 15 minutes.
When the job DOESN'T run successfully, the Errors.txt file is populated with many "Automation error, The remote procedure call failed." errors. When the job DOES run successfully, there is nothing written to Errors.txt.