[BUG]: Intermittent 408 timeouts calling db
See original GitHub issueDescription
I have an API endpoint that receives an email, and we store it in the database.
This is the code:
const { DbService } = require("m3o/db");
const dbService = new DbService(process.env.M3O_API_TOKEN)
// Wrapped in an http handler
await dbService.create({
record: {
id: email,
subscriptionId,
verified: false,
},
table: process.env.SUBSCRIBERS_DB_TABLE_NAME,
});
Most of the time it works fine, sometimes I get the 408:
{
Id: 'go.micro.client',
Code: 408,
Detail: 'context deadline exceeded',
Status: 'Request Timeout'
}
Happens locally and remotely. Thank you for your time!
Screenshots
No response
Additional information
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Troubleshoot Azure Cosmos DB HTTP 408 or request ...
In this article. The HTTP 408 error occurs if the SDK was unable to complete the request before the timeout limit occurred.
Read more >How To Fix the HTTP 408 Error (8 Solutions)
The 408 Request Timeout error means the request you sent to the website server took longer than the server was prepared to wait....
Read more >Intermittent 408 Errors In The Oracle iPlanet Web Server ...
On Oracle iPlanet Web Server 7.0u9 or newer, the problem is not observed and the request timeout is 30 seconds between subsequent requests, ......
Read more >How to Fix a 408 Request Timeout Error
Experiencing a 408 Request Timeout error? This guide goes over what you can do to troubleshoot both from the client and server side....
Read more >Getting 408 Request Timeout intermittently
I'm making and receiving free calls. Awesome! (I used the google-voice module for FreePBX - and currently that still breaks the PBX Tab...
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 FreeTop 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
Top GitHub Comments
OK thanks. Still doing some tweaks across the whole platform to reduce the incidence of timeouts. Have done a few more changes to loosen up timeouts which should help some more but please feel free to keep this issue open until you’re satisfied that it’s not a regular occurence
Thanks for the report. I’m looking at this now