Decisions, delivery, and billing
Read event history, recover failed destinations, and understand plan usage.
Read delivery history
Open a router and select View delivery history. Each event shows its state, matched label or fallback reason, confidence, usage status, and destination counts. Open the event for its sanitized input preview and the outcome of each destination.
Roggger removes common identity and credential fields from stored previews and from classification input. Do not include secrets that are unrelated to the routing decision.
Understand retries
Slack and generic webhooks have separate delivery records. One successful destination stays successful if another destination fails.
Transient failures retry automatically after increasing delays. Permanent failures and exhausted retries remain visible. Use Retry failed destination after the receiving service has recovered; Roggger retries that failed destination without resending successful ones.
Generic webhook delivery is at least once. A receiver should deduplicate by the stable event_id, because a timeout can occur after the receiver accepted a request.
Understand uncertainty and provider failure
Low-confidence and ambiguous results use the uncertainty route you configured. A classification-provider failure does not create a confident business label and does not consume a decision.
Manage plan usage
Open Billing from the routing desk to see the current plan and usage:
- Free: $0 for 50 total decisions. The allowance has no expiration and does not reset.
- Starter: $29 per month for 500 decisions per billing period.
- Scale: $79 per month for 3,000 decisions per billing period.
Stripe handles paid checkout, payment methods, invoices, plan changes, and cancellation. Upgrading raises the available allowance without erasing usage. A new paid billing period resets paid usage. Cancellation returns the account to any remaining Free allowance; decisions already used are not restored.
Privacy questions
Email privacy@roggger.com. Messages sent by Roggger come from Roggger (team@roggger.com).