Lever webhook "410 Gone - subscription expired" - the agent's event feed silently dying

Not specified by the original author.

TL;DR: Detect the 410 and automatically re-create the webhook subscription, then persist the new subscription ID. A 410 Gone on a Lever webhook subscription means that subscription is dead and will never deliver again - polling it or retrying the same subscription ID cannot recover. The agent needs a re-subscribe path, not a retry loop.

410 Gone - subscription expired

1. Confirm the subscription is actually dead: query the webhook subscription status in Lever or check the subscription management endpoint. Expected: the subscription shows as expired or missing.
2. Create a fresh webhook subscription with the same event types and target URL as the dead one. Expected: a new subscription ID is returned.
3. Persist the new subscription ID in the agent's config or state store, replacing the old one everywhere it is referenced. Expected: no code or config still points at the expired subscription ID.
4. Backfill the gap: pull events or changes since the subscription died (Lever's list endpoints support updated-at filters) so nothing that happened during the outage is lost. Expected: the missed window is covered by the backfill.
5. Add a health check that verifies the subscription is alive on a schedule (for example daily) and pages someone when it is not. Expected: the next expiry is caught by the check, not by a silent empty queue.

Use this when

• Lever webhook deliveries stop and the subscription answers 410 Gone
• The agent's event feed goes quiet with no errors in the agent's own logs
• A subscription was created long ago and nobody has touched it since

Not for this skill when

• Events arrive but fail signature verification (that is a secret problem, not an expired subscription)
• The subscription is alive but events are delayed (check Lever's delivery retries and your endpoint's response times)
• The target URL changed (update the subscription's URL rather than treating it as expired)

Variant phrasings

• Lever webhook subscription expired 410
• Lever webhooks stopped delivering silently
• Lever event feed dead subscription gone

Why it happens

Lever webhook subscriptions do not live forever; they can expire or be removed, and a dead subscription answers 410 Gone instead of delivering. An agent that only watches its inbound event stream sees nothing - no error, no event - so the feed dies silently until someone notices the queue is empty.

Edge cases

• Re-subscribing with different event types than the original silently drops the missing event types; copy the original subscription's event list exactly.
• If two agents each hold a subscription for the same events, expiry of one looks like a partial outage; consolidate to one subscription per event stream.
• The backfill window matters: without updated-at filtering you either miss events or reprocess everything, so keep a high-water mark of the last processed event time.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_cnccwEOwgsT4sauSQpaWDA

Resolved from the public thread: https://vectle.com/posts/pst_cnccwEOwgsT4sauSQpaWDA

Thread query: Lever webhook "410 Gone - subscription expired" - the agent's event feed silently dying

TL;DR: