Here at Pickaxe, we’ve been getting an increasing number of questions regarding Provider Errors - so we thought we’d send out a quick overview of what is happening behind the scenes in these situations, and how users can troubleshoot!
If you’re getting a “Provider Error” on one of your Pickaxes, it means just what the name implies - there is an issue with the model provider! Pickaxe attempted to get a response to the chat or form input from this provider (be it OpenAI, Anthropic, Google, or xAI), and for some reason, the model provider did not send Pickaxe any content in response. There are several potential causes for such an error:
- The provider is having internal issues. It is not uncommon for model providers to have bugs or downtime that prevent them from sending responses properly.
- A problem with your API. For users that still have their own key from a model provider, there is an issue with their account with the provider, or a problem with the key itself.
- The request was timed out. If Pickaxe has received no response from the model provider after a long period of time, the request may time out (this does not include situations in which an Action has been triggered and is running).
In these situations, there are a couple of useful troubleshooting options to get things up and running again:
- If you have your own API key, toggle it off (do not delete it) and try your prompt run using Pickaxe credits to see if it is a key-related issue
- Try checking out the status pages of your model provider to see whether they are having downtime or bugs. You can find these here:
- Try changing models by using a different provider and see if this removes the provider error
- If none of the above options are helpful, you can send us an email at info@pickaxeproject.com for further troubleshooting. When you send your email, please list the session ID(s) in which you received this error, which can be found in Message Insights, along with any extenuating circumstances that might impact your situation.
Importantly, Pro users have an added layer of protection preventing Provider Errors from cropping up, in the form of model fallbacks! If this is toggled on, your Pickaxe should automatically revert to your fallback model if an error is encountered with your chosen provider.
It’s also worth noting that if there is an error happening on the Pickaxe side, rather than the provider side, all users regardless of plan are equipped with a model fallback that should kick in and prevent this error.
I hope this is clarifying, and feel free to reference this if you get stuck on this error in the future!