(Reposting this; I originally posted this in the Development category)
Hi there,
I have a site with 7 jobs that connect using the OData provider (prices, products, orders, order lines and more). Every now and then (roughly every other day) all 7 jobs fail and I get an error report like this by email:
Activity BC Orders - 3. Update order fields on site http://domain.com was executed with an error.
Activity log information:
2024-01-06 19:50:10.369: Starting OData export.
2024-01-06 19:50:10.369: Begin synchronizing 'EcomOrders' to 'SalesOrder'.
2024-01-06 19:50:11.443: Job failed.
After some digging into monitoring, I found this:
2024-01-06 19:50:11.443: Integration job failed: 'BC Orders - 3. Update order fields'; logfile: /Files/System/Log/DataIntegration/BC Orders - 3. Update order fields20240106-1950102753913.log. System.AggregateException: One or more errors occurred.
System.Net.Http.HttpRequestException: An error occurred while sending the request.
System.Net.WebException: Unable to connect to the remote server
System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 12.34.56.78:7048
at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
This looks like a connectivity issue to the BC API.
Two questions:
1. Can the error that is logged into monitoring also be added to the job output and therefore error email? I know we talked about this before but we could really use it. These emails often get sent to the customer's IT department and without further info there are pretty useless. Explaining them how to relate timestamps in emails to certain items under monitoring to find the root cause of the error is just a bit too much. Having the actual error message in the log would solve a lot of issues.
2. Would a retry be helpful here? The next time the jobs run they work just fine so it seems to be an intermittent issue.
Imar
