Skip to main content
Start with the smallest safe check and preserve the evidence before changing configuration.

First response

Do not paste full logs into a public issue without removing domains, emails, tokens, candidate names, and database URLs.

Symptom table

Recovery recipes

Restart only the failed worker

Check the external proxy

Confirm Harly listens on 127.0.0.1:3000 (or HARLY_PORT) and that the proxy forwards the original Host and X-Forwarded-Proto headers. In external mode, Harly does not manage TLS.

Reconnect an integration

Disconnect the provider from Settings → Integrations, correct credentials or redirect URIs, reconnect, and run its test action. Do not create a second calendar event to work around a sync warning.

Capture an actionable issue

Include the Harly version, deployment mode, provider, UTC timestamp, command output with secrets redacted, request ID if present, and the last successful health check. See screenshots for visual evidence.