Q: I’m sending sales orders from a 3PL (NetSuite) to an FTP server. Sometimes my sales orders are erroneously marked as Sent in NetSuite, as the order never makes it to the FTP server. One error I’m getting is an FTP_AUTH_FAILED code with a message that it couldn’t connect to the SFTP server due to a connection timeout. I don’t see any retry data. How can I identify which sales orders were exported, but failed to import?
A: When a connection times out, retry data won’t be shown on your errors because the error did not occur due to a record failure, but a connection failure. In the case of FTP imports, initially the FTP connector tries to ping your FTP server. If this ping isn’t successful, there won’t be any retry data present. However, these jobs DO still retain the order data that failed to import, so they CAN be retried.
Check your integrator.io dashboard to see whether the Success number increments, but no file is imported. Make sure that your 3PL does not have any connection limits or throttling limits and that your FTP server did not go down intermittently.
To fetch data that failed to import:
- Open Chrome’s developer tools. Go to the Network tab. In your error list in integrator.io above, click your error.
- You’ll see some activity in the Network tab and should see a retries row and a joberrors row. You can search in the developer tools console for “api” to narrow down the results, if desired.
- Click the job errors row to display the Preview. Click the 0 row to expand it.
- Scroll down to where you see the _jobId and _retryId.
- In Postman, copy the _retryId into a GET call from Postman with this request, then click Send: https://api.integrator.io/v1/retries//signedURL
- You should get a signedURL link below.
- Copy that URL and open it in a new tab.
-
This will download the retry data file. Note that the SignedURL will expire in 10 minutes.
- Open the file. You should see your retry data
