Pulse Troubleshooting

My monitor is not running checks

Is the monitor active? Check GET /v1/pulse/:monitorId for "active": true.

Is the URL publicly accessible? Pulse checks from edge servers. Internal/private URLs, firewall-blocked endpoints, and URLs requiring login will fail.

Is the interval below your tier minimum? Intervals are coerced upward silently. See Tier Limits.

Webhooks are not arriving

Is webhook_url set on the monitor? Check with GET /v1/pulse/:monitorId. Webhooks require Starter tier or higher.

Has the consecutive threshold been reached? If consecutive_threshold: 3, the alert fires only after 3 consecutive failures. A single failure followed by recovery will not trigger a notification.

Is your webhook endpoint returning 2xx? Relay retries on 5xx but stops after 3 attempts. Test your endpoint with curl -X POST -d '{"test":true}' https://your-webhook-url.

Is cooldown suppressing the alert? After a DOWN notification, further DOWN notifications are suppressed for the cooldown period (default 5 minutes). State changes (DOWN to UP, UP to DOWN) always fire immediately.

Status shows UP but my endpoint is down

Is your health endpoint accurate? A /health that always returns 200 regardless of actual state will mask outages. Make your health check verify real dependencies (database, cache, etc.).

Is Pulse being rate-limited by your endpoint? If your endpoint rate-limits Pulse requests, checks may fail intermittently. Allow Pulse edge IPs or exempt health check paths.

Status shows DOWN but my endpoint is up

Is the URL correct? Verify protocol (https://, not http://), path, and port.

Is SSL valid? Pulse validates certificates by default. Expired, self-signed, or incomplete certificate chains cause DOWN status.

Is the response within timeout? Default timeout is 10 seconds. Slow endpoints (cold starts, heavy queries) may time out. Increase timeout up to 30000ms.

False positives (flapping monitors)

  • Increase consecutive_threshold to 2-3 to absorb transient network blips
  • Increase timeout if your endpoint has variable response times
  • Check if your endpoint rate-limits or geo-blocks Pulse edge servers

SSL certificate errors

  • Verify certificate is not expired
  • Ensure the full certificate chain is served (intermediate certs included)
  • Self-signed certs cause failures by default

Getting help

  1. Check status.solenoid.systems for platform issues
  2. Review Errors for specific error codes
  3. Email support@solenoid.systems with your monitor ID and time range