Automatic retries and webhook notifications
Temporary trouble is retried; persistent trouble becomes visible instead of disappearing into a log file.
- Retry limit
- Up to three transient retries
- Delivery
- Customer-configured webhook
- Verification
- Built-in test notification
Retry only when another attempt can help
The scheduler classifies failures before retrying. Temporary connection and service errors use a bounded backoff sequence. Storage-plan limits, invalid database credentials, missing native tools, and vault-key errors wait for customer action instead of repeating a doomed operation.
Webhook-only notifications
Customers can provide a webhook endpoint and choose which successful backups, failed backups, successful restores, failed restores, and schedule reminders should be delivered. The endpoint credential is write-only after saving, and a test action reports the destination’s real delivery result.
SaveState does not require or ship a separate Discord bot. A Discord webhook is one possible destination, but the integration model is the webhook itself.
Put this feature into a recovery plan
Install SaveState on Windows, protect a representative data set, and test the restore before it is urgent.
Choose a plan