The automation F01 - Recebe dados do webhook is responsible for receiving webhooks, and more than 20 executions have been stuck in Scheduled status since last night.
I have already tried:
Duplicating the automation;
Redirecting the webhooks to the new automation URL;
Resending the webhooks.
However, the new executions are also getting stuck in Scheduled .
The automation is active, but none of the executions are being processed.
I also tried cancelling runs, and although it shows “23 runs cancelled” on the bottom of the page, they are still in “Scheduled” status.
Details:
Automation: F01 - Recebe dados do webhook
Trigger: When a webhook is received
Execution status: Scheduled
More than 20 pending executions
Issue started last night
Could you please check whether there is an issue with the execution queue or a webhook processing limit?
Thank you very much for reporting this and for sharing all the details!
We’re already investigating the issue and will keep you updated here.
We haven’t made any changes to our automations over the past few weeks, so we first need to better understand what’s causing this issue. However, I’m confident we’ll be able to resolve it very quickly.
Thanks again for bringing this to our attention and for your patience!
Thank you so much for your patience while we investigated this!
Good news: Your automation is working again, and new webhooks are being processed normally.
We were able to identify the exact cause. On October 22, two fields were deleted from an app that your automation depends on. Since the automation was still referencing these fields, new executions could no longer start and remained in the “Scheduled” status. The duplicated automations inherited the same references, which explains why they were affected as well.
Importantly, there was no issue with Tape’s webhook processing, execution queue, or platform limits. All webhooks were successfully received, and execution runs were created. The issue was caused by the deleted fields that the automation was still trying to access.
We’ve now removed the outdated field references, and everything is running normally again. The previously stuck executions have been marked as failed, as none of them were actually processed.
A couple of things to keep in mind:
Please resend any webhooks from the affected period (starting October 22) that you still need processed. We’re happy to provide you with a detailed list of affected executions privately.
If you’ve redirected any webhooks to a duplicated automation, you can now safely point them back to the original one.
For the future, we’d recommend checking whether existing automations depend on specific fields before deleting them.
We’re also taking this as an opportunity to improve Tape further. We want to make dependencies like these easier to identify and ensure that configuration issues are surfaced much more clearly, so situations like this can be identified and resolved faster.
Thank you again for bringing this to our attention and for being such an active part of our community. We really appreciate it!
