When a source exceeds its limit
New triggers receive a rate-limit response. Respect the returned retry delay. A separate active-incident ceiling also limits new incidents for a service.
Incoming alert capacity and paid notification spending have separate safeguards. Configure both around the sources you connect and the channels your team needs.
Each integration key has a plan ceiling for new trigger events. Set a lower per-key ceiling to contain a noisy source. Acknowledge and resolve events do not consume fresh-trigger capacity; recognized idempotent retries do not consume it twice.
New triggers receive a rate-limit response. Respect the returned retry delay. A separate active-incident ceiling also limits new incidents for a service.
Trial supports 60 fresh triggers per minute per key, Team 300, Business 1,000, and Enterprise 5,000.
SMS and voice sends depend on balances, destination eligibility, configured spending caps, and send-velocity limits. A suppressed attempt records a reason in Delivery Activity.
Compare published allowancesIncluded allowances are used before prepaid credits for that channel. SMS cannot spend the voice balance and voice cannot spend the SMS balance.
A small grace balance can reach 10 credits below zero. Further paid sends stop until credits are restored; this is not a guarantee of unlimited incident delivery.
Push and email do not consume paid credits and can continue when they are selected, configured, and eligible under the incident's policy.
Automatic recharge requires an enabled policy and successful checks. It permits at most two purchase attempts for the channel within a rolling 24 hours.
Verify responder contact methods, current schedule coverage, matching policy steps, channel choices, and available credits. Use a labeled end-to-end test to confirm the configured path.
Start a workspace, connect a service, and make the next signal reach its owner.