• 2lzwqNqk8zKthC90uODsGP7Y1Ni
• 2m0FOGob2AiytuRD4JK3XhudSxO
Thanks, these are the root event IDs but are not running
Are there sub-event ID’s within the Split scenario? Maybe those will be shown as active
you’re not getting any Slack notifications, right?
That’s correct - no Slack notifications
For this specific workflow
I get notified of the others which are erroring out though
Could you share with me an URL for one event you get that errored out?
Btw what’s the API you’re getting rate-limited?
Are we not able to force stop these events? Or at least force an error on them so they stop running?
Please let me know, I am struggling to understand the delay
Eng did not find any running executions for this workflow
The issue you’re seeing in the UI is a false positive
Although the workflow looks like it’s running, or an execution is running, none are
If that was the case, then Supabase utilization would not have ramped on that specific day:
I have never had such high utilization
You have other workflows that make requests to Supabase, could it be they increased the usage?
None have increased in usage
Could you share one event that failed? Happy to look into the details
Looking at the Event History, they are all running successfully
So what was the status of the executions? Did they fail? Nothing is shown on the UI other than the ‘pause’ icon
I have attached another example - they just continue to grow in elapsed time with no actual output / logs
They timed out, this is a known bug in the UI that happens rarely