Error: timeout of 0ms exceeded
See original GitHub issueSentry reported a random error coming from Axios, Error: timeout of 0ms exceeded.
Under what circumstances would this error appear? We don’t have timeout settings configured, and 0ms seems like a mighty short time for any request to finish, so why is this error thrown?
It appears to have been a one off that is not readily reproducible, so I can’t provide test code, but the underlying network error seems to have been ECONNABORTED.
Axios version 0.18.0
Issue Analytics
- State:
- Created 4 years ago
- Reactions:86
- Comments:37 (1 by maintainers)
Top Results From Across the Web
Possible Unhandled Promise Rejection (id: 0) Error: timeout of ...
I want to show the total number of connections I have using the API I created, but when I run with the mobile...
Read more >Webui restore: Failed to list the revisions: Error: timeout of 0ms ...
After about 2 minutes, I get the following error as a notification: Failed to list the revisions: Error: timeout of 0ms exceeded.
Read more >What does 'timeout of 10,000ms exceeded' mean? - Quora
It means that the salesperson is compensated ten percent of whatever money they've brought into the company. Typically, this is represented by their...
Read more >Error: timeout of 0ms exceeded - - Bountysource
It appears to have been a one off that is not readily reproducible, so I can't provide test code, but the underlying network...
Read more >Handling timeout in Axios. Quick and easy - Medium
The default timeout is set to 0 which indicates no timeout. With that… ... Error: timeout of 2ms exceeded
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
For everyone enjoying this bug, I managed to catch this locally and match it up with a Sentry error report. It appears that this is the result of a genuine timeout, but the reporting of ‘0ms’ is simply a bug in axios’s reporting. So the errors are valid, however they are (or were in my case) real timeouts of significantly longer duration. @adamreisnz please could you re-tag this issue as a bug, which might get it some visibility.
We are seeing this when a stalled connection times out after 30 seconds. I think maybe the errors are valid, but the length of timeout is being misreported as 0.