The sync status button in the Linnworks header allows you to see currently running sync processes, queued sync jobs, and any errors for previous processes. If there are any errors, then the sync status button will also show the number of errors on a red background. It is recommended to check these sync errors, because they may indicate that some actions may be required from the user.
Single error messages during sync
- "An existing connection was forcibly closed by the remote host"
This error means that the server which Linnworks was connecting to has shut down the connection. It could be caused by issues with the sales channel servers or network connection between those servers and Linnworks sync servers.
- “Step: Synchronize orders for [SubSource], Unhandled Error is thrown: Step: Get all Amazon accounts Error: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - Not enough storage is available to complete this operation.)”
This error message means that Linnworks could not connect to the channel because there was a problem with the queue server.
These are normally "one-time" errors and next syncs run successfully. Such errors do not have a detrimental effect on your account. The sync process could be delayed a bit by such errors, but it will then pick up where it stopped and there will be no further complications.
If you received 1 such error over 100 successful syncs, then there is nothing to worry about.
Many error messages in a row
Many errors in a row will delay sync and may also indicate a larger problem with the sync and may require certain actions from the user.
In the automation logs, it can look like this:
- “Authorisation token is hard expired. User needs to generate a new token for this application.”
If the eBay token expires and no new token is generated, Linnworks will be unable to make API calls in that user's name. This has no effect on the user's eBay account, but it doesn't allow Linnworks to interact with eBay.
This article explains how this issue needs be fixed: eBay token expiry/generation
- "Start sync Error: Amazon SubmitInventoryChange: Feed Rejected"
The error means that Amazon is rejecting the feed even before processing it. This article explains how this issue needs be fixed: Amazon - inventory sync error: SubmitInventoryChange: Feed rejected
Amazon FBA errors during Order Sync
- "amazon.SSOFStatefulWorkflow.common.WorkflowPermanentException: SIPS invalid request on fulfillmentOrder='amazon.ShipmentInjectionWorkflow.data.MerchantRequest..."
This error can appear in the order sync logs when you are submitting an order to FBA. It indicates either a temporary connectivity issue on Amazon's end or an issue with the shipping address or shipping service.
To fix it:
- Check the shipping method and make sure it is used by FBA.
- Check the address lines and make sure that it doesn't have anything abnormal or unnecessary in it, such as an international province code.
- Try to submit this order again in a couple of minutes, if it was temporary, the order should submit this time without any issues.
If the above does not help, please contact Amazon FBA for assistance.
- "ERROR: The field PerUnitDeclaredValue has a value of GBP, was expecting EUR" - currency may vary.
To resolve this issue, you need to disable 'Send Declared Value' in channel settings and Save the changes:
- Go to Settings > Channel Integration > Edit Channel > FBA and disable the 'Send Declared Value' option.
- Now go to Open Orders > locate the order > right-click > Action > Bulk change > Clear shipping label info.
- Check in a while, the order should be submitted to the FBA successfully.