Skip to content
LLM

Common Issues

Use this page when a happy path breaks. Most issues come from missing local auth, the wrong selected inbox, expired claim links, or billing state that has not refreshed yet.

Symptom:

dispatch: command not found

Fix:

Terminal window
/bin/bash -c "$(curl -fsSL https://get.dispatchjoin.com/install_dispatch.sh)"
dispatch --version

Restart your shell if the command still is not found.

Check local auth:

Terminal window
dispatch status

Reconnect with one of:

Terminal window
dispatch inbox create
dispatch inbox claim --open
dispatch auth wallet --private-key-path ~/.config/dispatch/wallet.key

Use direct workspace or inbox keys only when you are wiring Dispatch into existing secret management.

Terminal window
dispatch inbox ls
dispatch inbox use <inbox_id>
dispatch inbox show

Mail commands use the selected inbox.

Fix:

Terminal window
dispatch inbox claim --open

Claim links are one-time and time-limited. Make sure you are signed into the intended web account before completing the claim.

Fix checklist:

  1. Confirm the account email was typed correctly.
  2. Use the resend verification action on the setup page.
  3. Check spam.
  4. If mail still does not arrive, submit a request at https://dispatchjoin.com/support.

Fix:

  1. Open https://dispatchjoin.com/reset-password.
  2. Request a reset email.
  3. Finish the reset with the emailed code.
  4. Sign back in and restore or claim the inbox.

Fix checklist:

Terminal window
dispatch inbox show
dispatch mail ls --folder all
dispatch mail code --folder spam
dispatch mail extract --kind code --limit 50

If the message has an unusual code format, open it in Mail Desk and read the code manually.

Fix checklist:

  1. Confirm the selected inbox with dispatch inbox show.

  2. Retry with a minimal text body:

    Terminal window
    dispatch mail send user@example.com "Test" --text "hello"
  3. Check plan or policy errors.

  4. Confirm the recipient address and spam folder.

Use the simplest path first:

  1. Open Billing in the web app.
  2. Complete the Team 1000 Stripe upgrade.
  3. Refresh Billing.
  4. Retry dispatch inbox create.

For wallet-backed payment:

Terminal window
dispatch inbox create next --swarm --private-key-path ~/.config/dispatch/wallet.key

Stripe Checkout Completed but Plan Did Not Update

Section titled “Stripe Checkout Completed but Plan Did Not Update”

Stripe upgrades are applied by webhook. Wait briefly, refresh Billing, then run:

Terminal window
dispatch billing ls

If the entitlement is still missing, contact support with account email, workspace id, and checkout timing.

x402 Payment Was Sent but Confirmation Fails

Section titled “x402 Payment Was Sent but Confirmation Fails”

Check:

  • The payment id is the quote payment_reference, not the transaction hash.
  • The --tx-hash is the actual on-chain transaction.
  • The confirming wallet is the payer wallet.
  • The transaction amount, recipient, asset, and chain match the quote.
  • Solana transactions may need more time to finalize.

Then retry:

Terminal window
dispatch billing confirm x402.<payment_reference> --chain eth --tx-hash 0xabc123 --private-key-path ~/.config/dispatch/wallet.key

Need Billing, Privacy, Export, Abuse, or Closure Help

Section titled “Need Billing, Privacy, Export, Abuse, or Closure Help”

Open https://dispatchjoin.com/support and include:

  • account email
  • workspace id
  • inbox address or inbox id
  • payment provider and transaction details, if relevant
  • the exact command or web flow that failed