Ask is not working
Recover from slow, failed or interrupted Ask requests, including stuck loading, cancelled runs and repeated errors.
Ask problems are usually transient: a slow request, a cancelled run, a very long conversation, or a provider outage. This page helps you distinguish those from a real fault.
The request is stuck loading
- Use the stop control to cancel rather than closing the tab.
- Start a new conversation and retry once.
- If it repeats, wait a minute — the provider may be rate limiting.
Responses are slow
- The conversation is very long — start a new one.
- The request needs live web research, which is genuinely slower.
- Many connected sources are being read — narrow the question to one source.
- Deep Strategy is selected — it costs and takes more by design.
The response does not answer the question
- The question was broad; OpenFeather answered the most likely reading.
- The expected capability is unavailable, and the notice was easy to miss.
- The topic changed mid-conversation and old context biased the answer — reset with a new conversation.
- The sources do not support the claim you expected; ask for the sources.
Repeated failures
If the same question fails repeatedly with a provider error, the provider is the problem. If it fails with an authorisation or limit error, it is local. Capture the exact error text, the time, and whether a general question works before reporting.
When the interface itself is broken
A blank composer, a control that will not open, or a response that stops mid-stream with no error are different problems from provider failures, and they are worth reporting precisely.
- Note the browser, the window width and the exact step where it stopped.
- Check whether a reload clears it — that distinguishes a rendering fault from a data problem.
- Try another conversation to see whether it is specific to one thread.
- Capture the console error if you are comfortable doing so.
Common questions
Do I get charged for a failed request?
No. Reserved credits are released when a request fails.
Should I retry immediately?
Yes for local errors. Wait briefly for provider rate limits to avoid making them worse.