I always get this error when I try to send a message Even when I tried to contact support start at +JSON Error while processing message Convert circular struct to property 'workflows_executions' | 'Object' object using index 0 -> object with constructor 'object' | ... | | Array object with constructor → ses https://cdn.discordapp.com/attachments/1147563033003044985/1147563033317621810/Screenshot_-.jpg?ex=6788859b&is=6787341b&hm=35ca9c31db4c326c50cd0a0130432cf2097d5ae43420e2aaa8ce8058e7be0256& https://cdn.discordapp.com/attachments/1147563033003044985/1147563033531523144/Screenshot_-.jpg?ex=6788859b&is=6787341b&hm=7b40eea0a1b062e81062bfb2ecc0b2e5ef5928563ea08f8f6564c12758eadc91& https://cdn.discordapp.com/attachments/1147563033003044985/1147563033816748113/Screenshot_-.jpg?ex=6788859b&is=6787341b&hm=1109817127f6ed5285c8351fad3984496075976fffe42a4a727cad2081333aa6&

We had a similar problem it was a total nightmare to fix. My theory was that some json was being processed by an internal function, and that was causing the error. So 1 by 1 I started deleting sub objects event.xxx and workflow.xxx. And that was indeed the problem. In our case, the workflow.apiSlackRequest.response.request object was the culprit. The request property within the API response creates a circular reference, as shown below:

{
  "apiSlackRequest": {
    "response": {
      "request": {
        "__sentry_xhr__": {
          "method": "GET",
          "url": "https://example.com/api",
          "body": null,
          "status_code": 200
        }
      }
    }
  }
}

I believe the circular reference arises in request -> res -> req -> request. To fix the issue, we deleted the problematic property response.request in a code execution card before proceeding. Here’s how:

try {
  if (workflow.apiSlackRequest && workflow.apiSlackRequest.response) {
    delete workflow.apiSlackRequest.response.request; // Fix circular reference
    bp.logger.info('Deleted: response.request');
  }
} catch (error) {
  bp.logger.error('Error clearing response.request:', error.message);
}