In deliverGoogleChatReply() (channel-X_UZamo0.js), the sendGoogleChatMessage call unconditionally passes thread: payload.replyToId. There is no error handling for INVALID_ARGUMENT on the thread parameter — the catch block logs the error and the caller retries, creating the loop.

TL;DR

Modify the deliverGoogleChatReply() function to handle INVALID_ARGUMENT errors for the thread parameter by retrying the send without the thread parameter.

Guidance

• Identify the deliverGoogleChatReply() function in channel-X_UZamo0.js and modify the sendGoogleChatMessage call to include error handling for INVALID_ARGUMENT errors.
• Implement a retry mechanism that removes the thread parameter if an INVALID_ARGUMENT error occurs, allowing the message to be posted as a new top-level message in the space.
• Consider adding a configuration option, such as channels.googlechat.threadReply: false, to disable thread replies entirely and prevent this issue.
• Verify that the modified function correctly handles INVALID_ARGUMENT errors and retries the send without the thread parameter.

Example

try {
  await sendGoogleChatMessage({
    account,
    space: spaceId,
    text: chunk,
    thread: payload.replyToId
  });
} catch (error) {
  if (error.code === 400 && error.message.includes('INVALID_ARGUMENT')) {
    // Retry without thread parameter
    await sendGoogleChatMessage({
      account,
      space: spaceId,
      text: chunk
    });
  } else {
    // Handle other errors
  }
}

Notes

This solution assumes that the sendGoogleChatMessage function is correctly implemented and only the error handling for INVALID_ARGUMENT errors needs to be added. Additionally, the channels.googlechat.threadReply: false configuration option may not be implemented, but it is suggested as a potential solution to prevent this issue.

Recommendation

Apply workaround by modifying the deliverGoogleChatReply() function to handle INVALID_ARGUMENT errors and retry the send without the thread parameter, as this will prevent the infinite retry loop and allow messages to be posted correctly.