What is the "Bad Request" Error Encountered by UMT4G7E5P in Google Calendar?

Bugs
1

This topic was automatically generated from Slack. You can find the original thread here.

{\"content\":[{\"type\":\"text\",\"text\":\"{\\n  \\\"os\\\": [\\n    {\\n      \\\"ts\\\": 1774287532896,\\n      \\\"k\\\": \\\"error\\\",\\n      \\\"err\\\": {\\n        \\\"name\\\": \\\"Error\\\",\\n        \\\"message\\\": \\\"Bad Request\\\",\\n        \\\"stack\\\": \\\"Error: Bad Request\\\\n    at makeErrorObservation (/var/task/node_modules/@lambda-v2/component-runtime/src/makeErrorObservation.js:7:11)\\\\n    at captureObservations (/var/task/node_modules/@lambda-v2/component-runtime/src/captureObservations.js:30:24)\\\\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\\\\n    at async run ([REDACTED])\\\\n    at async [REDACTED]\"\\n      }\\n    }\\n  ],\\n  \\\"exports\\\": {},\\n  \\\"t\\\": {\\n    \\\"ar\\\": 1774287521402,\\n    \\\"br\\\": 1774287521405,\\n    \\\"bp\\\": 1774287521405,\\n    \\\"bls\\\": 1774287521405,\\n    \\\"ble\\\": 1774287532912\\n  }\\n}\"}],\"isError\":true}

faced this issue in Google Calendar. Can you please check.

2

That looks like a 400 Bad Request error from the Google Calendar API, that’s not an error specific to Pipedream

3

you’ll need to take a look at the actual error to see where that failed

4

How to see that? This is retuned from pipedream MCP. I don’t see actual error returned.

5

What tool were you calling? Are you able to share example params that trigger this error?

6

I got the issue. LLM generated wrong calendar id. Hence the error. Any way we can surface the error sent by actual Google Caleandar API in the response?

7

normally it should, I’m not sure why there’s not that observability in this case. If you see this for another error / tool, let us know