These are issues that are being addressed currently. Right now in the Apps Script Early Access Program are two new additions that handle these cases. The first is native integration with stackdriver logging and the addition of google.script.run.withLogger().

First off for now you need to apply for the EAP:

https://developers.google.com/apps-script/guides/apps-script-eap

Stackdriver Logging:

To log to stackdriver the console object has been added to the server side.

code.gs

console.log('This will log to stackdriver')  

Check out the docs for all the methods of console.

https://developers.google.com/apps-script/guides/logging#stackdriver_logging

Example from the docs:

function measuringExecutionTime() {

  // A simple INFO log message, using sprintf() formatting.

  console.info('Timing the %s function (%d arguments)', 'myFunction', 1);



  // Log a JSON object at a DEBUG level. The log is labeled

  // with the message string in the log viewer, and the JSON content

  // is displayed in the expanded log structure under structPayload.

  var parameters = {

      isValid: true,

      content: 'some string',

      timestamp: new Date()

  };

  console.log({message: 'Function Input', initialData: parameters});



  var label = 'myFunction() time';  // Labels the timing log entry.

  console.time(label);              // Starts the timer.

  try {

    myFunction(parameters);         // Function to time.

  } catch (e) {

    // Logs an ERROR message.

    console.error('myFunction() yielded an error: ' + e);

  }

  console.timeEnd(label);     

  }

In addition you can also check Log Exceptions in the scripts properties. This will generate a stackdriver entry every time any error occurs in your script.

Error recovery in a web app

To recover in a web app from a failure you have access to the withFailureHandler() method found in the google.script.run object. With this you can register a callback in the event your script hits an exception.

Full documentation can be found at:

https://developers.google.com/apps-script/guides/html/reference/run

If you are doing server side checks with try...catch you may be getting an exception but gracefully handling it. In this case withFailureHandler() will not execute and onSuccessHandler() propably isnt the best place to handle errors. In the EAP there is now a withLogger method to google.script.run. For now there no documentation for google.script.run.withLogger(). I found it by digging through devtools. withLogger() allows you to register a function as a callback when ever a stackdriver entry is created. This is particularly helpful when you have log exceptions checked in your script properties. In this sense it is a bit like withFailureHandler() but it can be triggered by any stackdriver entry you add though the server-side console object.

index.html

<script>

  google.script.run

        .withSuccessHandler(function(){console.log('OK')})

        .withFailureHandler(function(e){console.error(e)})

        .withLogger(function(e){console.warn(The following log was generated:+e)})

        .serverFunctionCall();

</script>

code.gs

function serverFunctionCall(){

   console.log(This log will generate a callback);

   return true;



}