Bring a cost change to the team's attention.
Review cost and connection conditions in the workspace. For configured external destinations, follow the delivery record to see whether the notification reached its destination.
Explore the working sample →- Source
- Cost or connection condition
- Workspace
- Review the in-app alert
- External delivery
- Check the destination receipt
Choose a sample billing month
The fixed threshold below is an illustrative review cue, not a live alert configuration or an average savings claim.
Check the billing period, native currency, affected scope and freshness before interpreting a change.
Notification and receipt states- Net billed cost
- €84,240.60
- Sample review threshold
- €80,000.00
€4,240.60 above the sample threshold. Review the source and period before deciding what it means.
Destination state is separate
- In-app record
- Review needed
- External destination
- Not configured in this sample
- Confirmed receipt
- None
Follow the delivery from setup to receipt. A read notification does not resolve its source condition.
- Configured
- The workspace has an approved destination and its connection settings.
- Queued or attempted
- The event is awaiting delivery or a request was attempted. Neither confirms receipt.
- Acknowledged
- A supported external response confirms the relevant delivery outcome.
- Retry or dead letter
- Inspect the safe failure and next step. Do not paste signing secrets or raw webhook payloads into support.
Slack, Microsoft Teams and HTTPS webhook delivery depend on workspace configuration and the supported event. They do not imply every destination-specific ticket workflow is available.
Destination-specific deliveryKeep the next action tied to its source.
Review the finding, connection or delivery condition in the workspace before treating an alert as resolved.