Crashing function gives back status failed and status code 500, but the promise does go in onfulfilled, not in onrejected. This makes error handling hard.
First screenshot is code, second one result on browser console.
Causes code like this. 😦
This is expected because the function execution was created successfully. you can check the result and throw an exception in your client if you'd like
Recommended threads
- CORS errors in Obsidian custom plugin
Hi, anyone here familiar with obsidian community plugins? In short: it's a local first note app which supports writing your own add-ons / plugin But I keep get...
- > AppwriteException: The requested servi...
When trying to read or write from my database I get the following error: > AppwriteException: The requested service is disabled. You can enable the service from...
- Courtesy limit reset for non-profit migr...
Hi Team! I'm the architect for a 501(c)(3) non-profit project (Aaria's Blue Elephant) and we just hit our Free plan Database Read limit (currently at 164%). Th...