VisionScaper keeps trying when your receiver is down. It stops when it is clear nobody is listening.

Any HTTP 2xx answer. Anything else, a timeout, or no answer is a failure.

There are at most 6 tries per delivery. After the sixth, the delivery is marked Gave up.

• After 10 failed tries in a row for one alert, the alert is switched off and a note is made. You are told, and the message says to fix the address and turn it back on.
• If the receiver answers 410, the alert is switched off at once and that delivery is not retried. Zapier does this when a Zap is turned off.
• A success resets the count.
• Tests never count towards switching off.

1. Open Alerts to other tools.
2. Press the log button on an alert.
3. Each row shows when, what, and the result: Worked, Will try again (n so far), Gave up: reason, or a skip reason.

The log shows the last 50 tries. Old finished entries are cleaned up after 30 days.

1. Turn the alert back on first, if it is off.
2. On a Gave up row, press the retry button. Only a failed alert can be sent again.
3. It restarts with a fresh set of tries. Test entries cannot be retried.

Retries use WordPress scheduled events. A sweep also runs each 5 minutes and sends anything overdue, and frees deliveries stuck in “sending”. If WordPress cron is not running, retries are late. See Cron, caching, SSL and REST troubleshooting.

• Return 200 fast and do slow work afterwards.
• Check the delivery attempt number in X-VisionScaper-Attempt.
• If your plan stops including the feature, deliveries are skipped with “Your plan does not include this right now.”

• “The other side answered 500”: fix your receiver, then retry.
• “That address is not a public website.”: the host resolves to a private address.
• Nothing sent at all: no one is subscribed to that event, or the alert is off.

• Alerts (webhooks): setup and events
• Verifying an alert's HMAC-SHA256 signature
• Connecting Zapier (triggers and actions)
• Cron, WP-CLI, caching, SSL and REST troubleshooting (401, 403, 404)