Using the REST API v2 team-context webhook (event_type: FILE_COMMENT), registered via public OAuth on a Professional plan.
Problem
A newly registered webhook delivers events reliably for roughly the first hour, then Figma stops sending events entirely within about 1 to 4 hours, even though every health signal still looks fine.
In the dead state:
- GET /v2/webhooks/{id} returns status: ACTIVE, with the correct endpoint, event_type, and team context.
- GET /v2/webhooks/{id}/requests shows the earlier successful deliveries (all HTTP 200, no errors), and then NO further delivery attempts at all for events that happen hours later. Figma isn't attempting and failing -- it simply stops emitting.
- The OAuth access token is valid the whole time (GET /v1/me returns 200).
- The receiving endpoint responds 200 promptly; there are no timeouts or non-2xx responses in the requests log.
Steps to reproduce
1. Register a team-level FILE_COMMENT webhook via the REST v2 API (OAuth, Professional plan).
2. Add comments -- they deliver fine (HTTP 200).
3. Add another comment about an hour later -- still delivers.
4. Wait a few more hours, then add a comment -- no delivery. The webhook is still ACTIVE and the token is still valid, but /requests shows no attempt for it.
Expected
An ACTIVE webhook with a valid token keeps delivering events indefinitely.
Actual
Event emission silently stops after ~1 to 4 hours. Deleting and re-registering the webhook restores delivery, but only for another ~1 to 4 hours, then it recurs.
Reproduced on two independent accounts/teams, both Professional, including a brand-new account.
Question
Why does an ACTIVE webhook with a valid token stop emitting events after a few hours? Is there an undocumented inactivity timeout, or a known issue with v2 team webhooks?
