{2 items
"messages":“The API is unreachable, please contact the API provider”
“info”:“Your Client (working) —> Gateway (working) —> API (not working)”
}
We are facing this issue when we sync product :- {“messages”:“The API is unreachable, please contact the API provider”, “info”: “Your Client (working) —> Gateway (working) —> API (not working)”}
Sorry for the late reply. (Please create a new or root comment instead of sub-comments.
This is because RapidAPI only notifies me of root comments)
I believe the endpoint is up and running.
We have a self healing infrastructure (based on kubernetes).
It might take some time to detect and correct those errors.
Also whenever you get a 504 error it means that our service is down.
Any other error means something went wrong on RapidAPI’s end or your end.
Incase of a 504 error:
retry using exponential backoff.
example
retry after 30s, 1m, 2m, 4m, 4m, 4m …
(You don’t need to go longer than 4 minutes)
This is necessary to help our infrastructure heal fast.
We have identified and fixed the issue. All endpoints except for website extraction are now working. We will require a little more time to fix the website extraction endpoint. Thanks for reporting the issue. In the mean time while we work on the fix for website extraction do you have any more queries?
We are facing this issue when we sync product :- {“messages”:“The API is unreachable, please contact the API provider”, “info”: “Your Client (working) —> Gateway (working) —> API (not working)”}
Sorry for the late reply. (Please create a new or root comment instead of sub-comments.
This is because RapidAPI only notifies me of root comments)
I believe the endpoint is up and running.
We have a self healing infrastructure (based on kubernetes).
It might take some time to detect and correct those errors.
Also whenever you get a 504 error it means that our service is down.
Any other error means something went wrong on RapidAPI’s end or your end.
Incase of a 504 error:
retry using exponential backoff.
example
retry after 30s, 1m, 2m, 4m, 4m, 4m …
(You don’t need to go longer than 4 minutes)
This is necessary to help our infrastructure heal fast.
Same is happening with me? any idea why?
Hi Mike,
Hi Mike,
We have identified and fixed the issue. All endpoints except for website extraction are now working. We will require a little more time to fix the website extraction endpoint. Thanks for reporting the issue. In the mean time while we work on the fix for website extraction do you have any more queries?
Thanks.