
I am getting lots of timeouts since yesterday's incident, speaking in terms of multiple 100s just today. Also, very frequently, request are taking lots of time to complete (more than 5 seconds). It is happening for all CRUD operations and also both for Auth, Database, Messaging etc.
What is interesting, this is not the first time - this always happens after the incident with database, something is still broken on the Cloud side. Even if incident is resolved quickly I still get very bad experience for many days after.
I have some retry and mitigation logic for some of those fails but it is not a silver bullet and my error reporting is still going crazy plus I am getting bad reviews on the stores that will probably always stay there 😕.
Recommended threads
- Database attribute labeled "stuck", cann...
See screenshots. I'm on self-hosted, 1.6.1. I can click options -> delete and then get the green success toast it was deleted, but when I refresh it's still th...
- About the Image Transformations
Hey I wanted to ask what is the quota for Image Transformations on getFilePreview endpoint for github student plan. As far as I know, it's similar to Basic Pro ...
- Can't update the default value of an exi...
It is giving us an error: "Minimum value must be lesser than maximum value", when we update the existing attribute in one of our database.
