FAQ & Troubleshooting

Emails are still forwarded to your targets, but they won't be stored in the dashboard. You'll see a warning in the logs.

Yes. Each webhook has separate Resend and SendGrid URLs. You can configure different providers per webhook.

Three checks: (1) sender matches FORWARD_FROM_EMAIL, (2) subject has 2+ [FWD] prefixes, (3) rate limit of 10 emails/minute per webhook.

Failed deliveries are automatically retried up to 3 times with exponential backoff (1min, 5min, 15min). After 3 failures, you receive a notification.

Every 2 minutes, configured via Vercel cron.

PostgreSQL 14 and above. SSL connections are recommended.

No. For security, private/internal IP addresses (127.x, 10.x, 192.168.x) are blocked. Use a cloud-hosted provider like Neon or Supabase.

Data is stored independently in each backend. Switching does not migrate data between Managed Database and PostgreSQL.

Go to Dashboard > Settings > API Keys (Pro plan required).

API: 100 requests/minute per key. Webhook ingest: 60/minute per IP. Auth routes: 10/minute per IP.

• Verify the shared secret matches your email provider configuration
• For Resend: ensure Svix signature verification matches the webhook secret
• For SendGrid: include x-webhook-secret header

Rate limit exceeded. Wait for the window to reset (check the X-RateLimit-Reset response header).

• Check the webhook is active (green status in dashboard)
• Verify forwarding email addresses are correct
• Check for loop detection in logs