Troubleshooting Inventory Feeds

When updating an Inventory Feed to Active status, our system will validate that the target S3 bucket has the correct configuration.

Option 1: Confirm the target bucket has the correct policy applied

If the policy is correctly applied, check Option 2.

Option 2: Review the failure response

As part of the update mutation, the failure response will provide the context of what is failing. This can help you to fix the incorrect configuration.

An Inventory Feed Run may have failed for a range of reasons. Depending on these reasons, you may be unable to take proactive action.

Option 1: Check the Inventory Feed Run error message

The error message saved against an Inventory Feed Run will be able to provide context on what has caused the failure. If it is a configuration issue, you can update the Inventory Feed to fix this issue. Other times, it may be a random failure. At that point, the next Inventory Feed Run will catch the Inventory Feed back up to the latest view of Inventory Availability.

Option 2: Target S3 bucket configuration

If anything changes with the configuration of the target S3 bucket, this may cause Inventory Feed Runs to fail consistently. If this has happened, the first piece to try would be to reset the configuration. If that isn’t possible, you may need to create a new Inventory Feed to replace the broken one.