Skip to content

Logs

Purpose

Streaming live logs from any deployed Worker via wrangler tail.

Commands

npx wrangler tail --config workers/api/wrangler.jsonc                # [READ-ONLY]
npx wrangler tail --config apps/corporate-web/wrangler.jsonc         # [READ-ONLY]
npx wrangler tail --config apps/software-web/wrangler.jsonc          # [READ-ONLY]
npx wrangler tail --config apps/logistics-web/wrangler.jsonc         # [READ-ONLY]
npx wrangler tail --config apps/commerce-web/wrangler.jsonc          # [READ-ONLY]
npx wrangler tail --config apps/embroidery-web/wrangler.jsonc        # [READ-ONLY]
npx wrangler tail --config apps/admin-web/wrangler.jsonc             # [READ-ONLY]
npx wrangler tail --config apps/investors-web/wrangler.jsonc         # [READ-ONLY]

Step-by-step execution

  1. Run the command for the Worker you suspect is misbehaving.
  2. Reproduce the issue (hit the URL, submit the form, call the API) while the tail is running.
  3. Read the streamed request/response/exception for that specific invocation.
  4. Ctrl+C to stop streaming - this does not affect the running Worker.

Expected result

A live stream of request logs (method, path, status, duration) and any console.log/exception output from the Worker's own code, appearing as requests happen in real time.

Notes

  • Requires the same CLOUDFLARE_API_TOKEN/account auth as any other wrangler command against production - see Cloudflare → Wrangler.
  • admin-web runs with run_worker_first: true, so every request to admin.akshayagroupglobal.com goes through its Worker and will appear in its tail - not just API-style calls (see Cloudflare → Static Assets).
  • No log persistence beyond the live stream - if you need a historical record, capture the tail output yourself (e.g., wrangler tail ... | tee incident.log) at the time of the incident.