Hi Team,
Webhook not working. Kindly check the logs of my server.
02/14/2023 10:00 am : url https://eo392flqygvb7e0.m.pipedream.net
02/14/2023 10:00 am : *********** ERROR for webhook url https://eo392flqygvb7e0.m.pipedream.net is Server error: POST [https://eo392flqygvb7e0.m.pipedream.net](https://eo392flqygvb7e0.m.pipedream.net/) resulted in a 503 Service Temporarily Unavailable response:
Hi @sumitrathi , Pipedream experienced a major incident from ~2am UTC until 7:06 UTC today (details / incident log here). We use AWS Lambda as a part of our backend to process workflow events. AWS experienced issues due to the scale of workflows we run, and had to throttle our traffic, which triggered the incident. We got in touch with the AWS team, and they shipped a patch to address the issue around 6:00 UTC. We began to process the backlog of events. By 7:06 UTC, all issues were resolved and incoming events were processing as normal.
Between 3:51 AM UTC to 6:04 AM, we had to disable incoming events due to some of the load issues we were experiencing. Events sent during this time may be retried by the source services (e.g. webhook services). At 6:04am, we re-enabled the collection of incoming events again.
We’ll be publishing a detailed post-mortem, and will share that when we have it.
I’m new to this, but also experiencing not being able to set up workflows in Monday.com.
Having first this error:
TypeError: Cannot destructure property ‘items’ of ‘(intermediate value).data.boards[0]’ as it is undefined.
at Object.commonDeploy (file:///var/task/user/sources/common/common-webhook.mjs:65:15)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async Object.deploy (file:///var/task/user/sources/column-value-updated/column-value-updated.mjs:14:7)
at async /var/task/index.js:95:13
at async captureObservations (/var/task/node_modules/@lambda-v2/component-runtime/src/captureObservations.js:28:5)
at async Runtime.exports.main [as handler] (/var/task/index.js:60:20)
And then when choosing a different trigger having this error:
Error: Failed to establish webhook
at Object.activate (file:///var/task/user/sources/common/common-webhook.mjs:28:15)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async /var/task/index.js:95:13
at async captureObservations (/var/task/node_modules/@lambda-v2/component-runtime/src/captureObservations.js:28:5)
at async Runtime.exports.main [as handler] (/var/task/index.js:60:20)
I am also not able to find the boards I want to use a trigger from. Sometimes they show up, and sometimes they don’t. When I work with the monday.com api outside of pipedream, everything works well. Is this still an issue or am I doing something wrong?
I believe this is another issue, not related to Pipedream incident. Would you mind sharing the Monday.com trigger/action that you’re using for me to reproduce?
Thank you for raising this issue. I can reproduce this issue! I have created a ticket here to track it. Pipedream component dev will take a look at it soon! Kindly subscribe to the ticket to be noticed when it is landed!