Third-Party Services & Debugging

Quick reference for the external services Eventuall depends on and where to look when something breaks.

Services Reference

Common Debugging Quick Reference

Viewing Logs

Dev server logs are written to /tmp/eventuall-dev-logs/ with timestamped filenames:

# Full status of all services
./scripts/dev-server.sh status

# View recent logs
./scripts/dev-server.sh logs

# Tail logs in real-time
./scripts/dev-server.sh tail

Workers logs in production/preview use wrangler tail:

wrangler tail --env production

Client telemetry is stored in the client_logs table in D1. Query it with:

SELECT * FROM client_logs
WHERE level = 'error'
ORDER BY clientTimestamp DESC
LIMIT 50;

Database (D1)

# Query local D1 (development)
wrangler d1 execute eventuall-workers-db --local --command "SELECT * FROM users LIMIT 5"

# Query remote D1 (production)
wrangler d1 execute eventuall-workers-db --remote --command "SELECT * FROM users LIMIT 5"

# Apply pending migrations locally
pnpm migrate:local

# Generate a new migration
pnpm migrate:generate

Use Drizzle Kit for schema exploration:

npx drizzle-kit studio

Note: Local D1 is a SQLite file — changes don't sync to remote. If debugging a production issue, always use --remote.

Workers & Durable Objects

# Deploy workers
wrangler deploy

# Tail worker logs (real-time)
wrangler tail

# Inspect Durable Object storage (local dev)
# DO state persists across requests — restart wrangler to clear it

Durable Object state is scoped per ID. If state seems stale after a code change, the old serialized state may be incompatible with new code. Restart the local Workers dev server to reset.

Webhooks

Several services send webhooks into the application:

When debugging webhook issues:

1. Check the service's dashboard for delivery status and recent payloads
2. Check worker/server logs for parsing or validation errors
3. Verify the webhook signing secret matches what's configured in Doppler

Environment Variables

Environment variables flow through a specific chain:

Doppler → Terraform → start-dev.sh / .dev.vars → Runtime

To check current values:

# See what Doppler has for the current environment
doppler secrets

# Check what Terraform outputs (from terraform/ directory)
terraform output

# Verify what the dev server loaded
# Check start-dev.sh or .dev.vars files in each app directory

If a variable is missing at runtime, trace it backwards through this chain.

When X Breaks, Check Y