Descriptive errors are crucial for debugging and simply cannot be found with Atlas App Services !
1) If an error occurs - the whole function cascade is terminated - not only the steps following the error but also the ones prior to it. i.e. if a console.log was applied on a function that should have produced information before the error - that too will disappear and will not be displayed.
2) That is why it can take hours to find the exact location of the error this way, by trial and error.
3) If I was clever enough to console.error exactly the correct place where the error originated - the error is still minimalistically lean and uninformative.

It is absolutely critical for the ability to call functions from within functions - to enable error construction, such as with calling "new Error()" with a regular node.js app, that will deliver information regarding the origin function, the line of code from which the error was invoked, and a message regarding the error.
The lack of error constructor triples the coding time for any app larger than couple of functions.