Add Pause/Enable control for webhooks
-
Add Pause/Enable control for webhooksAdd a Pause/Enable button to each webhook so you can stop deliveries without deleting the webhook and resume them later; pausing also cancels any in‑flight retries and enabling does not replay events missed while paused.
-
Add manual Redeliver for webhook delivery rowsAdd a Redeliver action in the delivery log so owners/admins can re‑fire any non‑success delivery on demand; redeliver rebuilds the payload if needed and restarts the retry budget so a long‑failed delivery can be retried.
-
Add per‑webhook health dot to the webhook listShow a small status dot beside each webhook name that summarises recent delivery health (green = delivered, red = failed, amber = retrying, grey = no deliveries yet) so you can spot broken endpoints without opening each log.
-
Add webhook delivery KPIs to the Admin overviewSurface platform‑wide webhook health on the founder Admin overview with tiles for recent failed deliveries (7d) and the current pending‑retry backlog so platform operators can spot cross‑team delivery outages early.
-
Fix Free team member cap by counting membershipsFix the invite limit check to count team memberships (not the legacy users.teamId field) so Free teams are correctly prevented from exceeding the member cap when members join via invites.
-
Fix owner/admin detection for notifications and plan resolutionFix owner/admin lookup to use the memberships model so release approval emails go to the correct people and the founder‑owned team bypass for Pro correctly applies when a founder is an owner on any team.
-
Improve webhook reliability with durable retriesMake webhook delivery durable: events get a short inline retry burst and — if still failing — are queued for hours‑scale retries so receivers that are down for minutes or hours have another chance to receive the event; dashboard rows show retrying state and each attempt now times out after 10s.
-
Limit subscriber email concurrency to avoid provider rate limitsLimit concurrent subscriber sends (small pool) during release fan‑out to avoid hammering email providers and reduce lost sends, and update the fan‑out log to report real sent/failed counts.
-
Add central product slug validation with reserved‑word blockingCentralise and lock down product slug rules (shape, length, reserved words) used by the slug check and product creation flows; founders can still claim reserved slugs for internal/demo products, and mixed‑case slugs are rejected rather than silently lowercased.