Troubleshooting & Support

Use this checklist to resolve common issues before opening a support ticket.

Console & Authentication

• Ensure your API key or JWT hasn’t expired (relay account show will confirm).
• For SSO issues, clear your browser session and retry, or request a device-code login from the CLI.
• Status page: status.deployrelay.com

Deployments

• Verify environment variables (DEPLOYMENT_MODE, database/cache URLs) match the target setup.
• Rerun python3 dev_process/validation/quality_gate_runner.py to confirm smoke/performance/audit checks before redeploying.
• Check Cloudflare Pages build logs for documentation deploys.

Runtime & Executions

• Use relay functions logs <rufid> for real-time logs and error traces.
• Confirm namespace budgets and policies in the console—blocked executions often stem from quota enforcement.
• Review Datadog dashboards for latency or error spikes; adjust alerts as needed.

Marketplace & Billing

• Ensure your Stripe integration is active (production accounts only).
• Marketplace purchases require published pricing tiers and active entitlements.
• For billing or entitlement disputes, email support@deployrelay.com with the transaction ID.

Contacting Relay Support

When opening a ticket, include:

• Project/tenant ID and environment (staging, production, etc.)
• Relevant RUFID or execution ID
• Timestamps and logs/screenshots illustrating the issue
• Steps already taken to troubleshoot

Support channels:

• Email: support@deployrelay.com
• Slack: Customer workspace #relay-support
• Emergency (P0 incidents): follow the escalation runbook in the console