IssueTracker

Problem you have encountered:

Stack traces for Node.js services are incomplete if they contain calls to async functions, even though the messages in Logs Explorer contain the complete call stack. This can cause unrelated errors to be grouped.

For example, I see the following log entry in Logs Explorer:

Error: Lorem ipsum dolor sit amet
    at logError (/workspace/function.js:3:15)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async doFirst (/workspace/function.js:7:2)
    at async module.exports.handler (/workspace/function.js:15:2)

On the Error Reporting Details page, it looks like this (in both the raw and parsed modes):

Error: Lorem ipsum dolor sit amet
    at logError (/workspace/function.js:3:15)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) 

What you expected to happen:

The error details should contain the complete stack trace.

Steps to reproduce:

Here's the code that was used to generate the logs. It creates two different errors in order to demonstrate that they end up as a single Error Reporting group. Removing the await Promise.resolve() line separates them into two different errors, which is what I'd expect in both cases.

function.js

async function logError(message) {
  await Promise.resolve(); // Comment out this line for non-async stack frames
  console.log(new Error(message));
}

async function doFirst() {
  await logError('Lorem ipsum dolor sit amet');
}

async function doSecond() {
  await logError('consectetur adipiscing elit');
}

module.exports.handler = async function(req, res) {
  await doFirst();
  await doSecond();
  res.end();
}

It was deployed as a Cloud Function with the command gcloud functions deploy --runtime=nodejs16 --trigger-http --entry-point=handler stack-trace.