Overnight, all event delivery on my account stopped. It worked fine at 11pm yesterday; by this morning nothing fires. Both webhooks and custom actions are affected.
Here’s what I’ve confirmed:
My webhook (metadata.value.updated) and my three custom actions (Publish, Recall, Recall and Delete) all show active: true via the API and “Active” in the UI. Event keys and URLs are correct. Workspace scope is correct, the files I’m modifying are in the right workspace.
When I trigger a custom action in the UI, I get a spinner and then “loading timed out.” So the action is firing on the client side, but delivery never completes.
As a test, I pointed my Publish custom action at an independent third-party capture URL (webhook.cool). I clicked the action. Zero requests arrived at that URL. So this is not my endpoint. My own endpoint works fine when I POST to it directly; the problem is that Frame.io’s outbound delivery isn’t reaching any destination.
One clue that points at migration: earlier this morning one of my webhooks returned is_active: null via the API (not true, not false). Your docs describe this as a migration artifact, webhooks get auto-disabled and land in a null state when an account migrates to V4. Is it possible my account migrated overnight, and event delivery didn’t come back up correctly?
Could someone from Frame.io inspect the delivery/failure log for my account? I’d like to know whether events are being attempted at all, and if so, why they’re not reaching the destination.
Happy to run any tests or share more. Given my upcoming event timing, a quick look at whether delivery is firing on your side would help enormously. Thank you!