Skip to main content
Starter Kit - Ships with your template. You own it - modify freely.
Debug ensembles provide essential tools for testing and troubleshooting your Conductor deployment. These lightweight workflows help verify connectivity, inspect requests, and test timeout handling.

Ping

Endpoint: GET /debug/ping or HEAD /debug/ping File: ensembles/debug/ping.yaml Minimal ping endpoint that returns “pong” immediately. Ideal for verifying basic routing and connectivity. Response:
Use Cases:
  • Health checks and uptime monitoring
  • Verifying worker deployment and routing
  • Testing basic HTTP connectivity
  • CI/CD pipeline validation

Echo

Endpoint: GET|POST|PUT|PATCH|DELETE /debug/echo File: ensembles/debug/echo.yaml Echoes back the complete request including method, path, query parameters, headers, and body. Response:
Use Cases:
  • Testing webhook integrations
  • Debugging API client implementations
  • Verifying request formatting
  • Inspecting proxy/CDN modifications

Headers

Endpoint: GET /debug/headers File: ensembles/debug/headers.yaml Inspects and categorizes all request headers by type (Cloudflare, authentication, standard, custom). Response:
Security: Automatically redacts Authorization and X-Api-* headers to prevent credential leakage in logs. Use Cases:
  • Debugging CORS configuration
  • Verifying auth header propagation
  • Inspecting CDN/proxy header injection
  • Testing custom header handling

Info

Endpoint: GET /debug/info File: ensembles/debug/info.yaml
Protected Endpoint - Requires authentication via Bearer token or API key. Do NOT expose publicly in production.
Returns system information including Conductor configuration, available bindings, runtime details, and environment variables. Authentication Required:
  • Bearer token: Authorization: Bearer <token>
  • API key: X-API-Key: <key>
Response:
Use Cases:
  • Debugging environment configuration
  • Verifying binding availability
  • Inspecting runtime state
  • Troubleshooting authentication
  • Internal diagnostics
Security Best Practices:
  • Never set public: true on this endpoint
  • Use strong API keys in production
  • Rotate credentials regularly
  • Monitor access logs
  • Disable in production if not actively debugging

Slow

Endpoint: GET /debug/slow?ms=2000 File: ensembles/debug/slow.yaml Responds after a configurable delay (defaults to 1000ms). Useful for testing timeout handling and loading states. Query Parameters:
  • ms (optional): Delay in milliseconds (default: 1000)
Example: GET /debug/slow?ms=5000 (delays 5 seconds) Response:
Use Cases:
  • Testing timeout configurations
  • Simulating slow API responses
  • Testing loading states in UI
  • Debugging retry logic
  • Performance testing
Notes:
  • Cloudflare Workers free tier may have limited scheduler.wait() support
  • Actual delay may vary slightly from requested delay
  • Maximum delay depends on Worker timeout limits

Quick Reference

Ping

Quick connectivity verification

Echo

Mirror complete request details

Headers

Inspect categorized headers

Info

System diagnostics (protected)

Slow

Configurable delay testing