In some rare cases, you might get an error message when navigating your Sizefox Dashboard or in the widget itself.
Here you can find an overview of the main reasons behind them, and how to troubleshoot.
404 In this case, the CTA-button will not show up on the product page.
This error indicates that Sizefox was not able to match the product you are currently viewing to a size chart. This mostly happens because of 2 reasons:
No query attached to a size chart matches the product (you would also be able to visualize this in the query-matcher component in the Admin)
The size chart matching the product has not been published.
401 Unauthorised: Your session is invalid and has most likely timed out after being idle for too long. Please log in again.
400 Bad Request: Usually indicates that the server failed validating the request. The Admin should have made you aware of this before dispatching the request. Please contact support at email@example.com if the problem persists.
500 Errors: These errors usually indicate that you are trying to perform an action that the backend cannot execute because of other restrictions. Examples are:
Creating an account for an email that is already registered.
Trying to link a Shop to an Org that is already linked to another Org (each shop can only exist within the same org) .
Wrong order of commands (such as trying to delete a size chart that has just been deleted in another browser-window).
429 on any request to api.sizefox.com: You are experiencing a rate limit. Possible reasons are:
Too many requests within a certain time from the same IP address
Too many requests to Sizefox for the given Org (sizefox-account which can be home to multiple web shops)
If you feel the limits are too conservative for your shop, please contact us at this mail address: firstname.lastname@example.org
You should not experience other errors when using Sizefox as intended. If you persistently experience other error-responses, please contact support at email@example.com.
In your message, please add the exact time at which you experienced the issue and the request that led to the error message, along with a short description of what actions you were performing to your support-inquiry.