Skip to main content

Troubleshooting

CLI says config is missing​

Run:

tiden setup

Or set config manually:

tiden config set baseUrl https://app.tiden.ai
printf '%s' "$TOKEN" | tiden config set apiToken -
tiden config verify

Add --workspace-id <id> to config set apiToken and config set baseUrl when more than one workspace login is already stored.

Check environment variables if CI behaves differently from local:

env | grep TIDEN_

CLI returns auth error​

A rejected token (401) returns exit code 2.

Fixes:

  • Confirm the token was copied correctly.
  • Confirm it has not been revoked.
  • Confirm TIDEN_BASE_URL points to the right Tiden instance.
  • Run tiden config verify.

CLI says a repository is bound to a workspace I cannot access​

This repository is bound to workspace <id> (<name>), and none of your
logged-in accounts is a member.

Cause: no account you are logged in with belongs to that workspace.

Fix: run tiden auth login to add or sign back in with an account that is a member, or tiden setup --workspace-id <id>.

CLI says a product is not visible to any logged-in account​

Product <id> is not visible to any logged-in account.

Cause: none of your logged-in accounts can see that product. A stored product token counts as one of them: it sees only its own product, so the CLI skips it for any other product.

Fix: run tiden setup with the account that owns the product, or store a product token from that product's Product settings > API tokens.

CLI says the repository needs a choice​

This repository needs a choice: …

Cause: this is a repository Tiden has not seen before and you are logged in with more than one account, or its git remote is known under more than one product.

Fix: run tiden workspace use <id> or tiden product bind --product-id <id>. Coding agents can pass --workspace-id instead of answering the prompt.

CLI says a token was rejected​

Token for <account> was rejected and no other logged-in account is a member
of workspace <id>.

Cause: the stored token for that account no longer works, and no other logged-in account can take its place.

Fix: run tiden auth login to replace the token (or tiden auth logout to remove the stale entry first), or run tiden setup --workspace-id <id>.

API token is refused with 403​

With the token in TIDEN_API_TOKEN, a 403 returns exit code 1. Exit code 2 is reserved for a rejected token; with a 403 the token is valid and one of its limits refused the call. The message says which limit. A stored token behaves differently when it cannot see the product: the CLI skips it and reports that the product is not visible, with exit code 2.

this API token is limited to product <id>: a product token with full access was used on another product. Use a token from Product settings > API tokens of that product, or check TIDEN_PRODUCT_ID.

this API token can only publish test runs for product <id>: a publish-only token was used on another product, or made a call other than publishing test runs, such as tiden release create, a source map upload, or tiden test ingest. Use a product token with Full access to this product.

this API token can only publish runs to intent branches: a token with Only intent branches named the intent session of another branch, or reported results to, completed, or aborted a run that was not created by a token with Only intent branches.

See API authentication.

API token cannot call an endpoint​

API tokens can call only the public API surface. If the endpoint manages organization members, billing, credentials, token creation, profile security, or other web-only admin state, use the web app.

Review link proposals before merge:

tiden branch link-proposals list --product-id <product-id> --name <branch-name>

Accept or reject proposals:

tiden branch link-proposals review \
  --product-id <product-id> \
  --name <branch-name> \
  --decision accepted \
  --all-proposed

Branch merge has conflicts​

Open the Branches page, inspect each conflict, and choose keep branch or keep main. Use CLI auto-resolve only when the direction is obvious.

An intent branch did not merge, or merged when I did not expect it​

Open the branch and read the merge box. It names what the branch waits for.

  • An open pull request or an active agent session. The branch merges after they finish and 24 hours pass without activity.
  • On hold. Release the hold with tiden intent hold --clear --intent <branch> or Release hold on the branch page.
  • Partially delivered. Some promises are open. Continue the intent, or the shipped part merges after 7 days.
  • Abandoned. No pull request merged and 7 days passed without activity. Any activity reopens the branch.
  • Automatic merge is off for this product. Turn on Automatic intent merge in the product settings.

A branch a person closed waits for nothing: it has no merge box, its page reads Closed by <name> · <when>, and it does not merge or reopen. Start a new intent to continue the work.

For the rules behind a merge you did not expect, see Automatic merge of intent branches. To keep a branch from merging, set a hold before the 24 hours end. Tiden has no undo for a merge. Start a new intent with tiden intent reopen to correct it.

Error events do not appear​

Check:

  • The DSN came from the same product you are viewing.
  • The app is sending to the ingest host in the DSN.
  • The SDK has a release and environment if you are filtering by them.
  • The body is under 1 MiB.
  • The DSN key has not been revoked.
  • The Issues page is not still showing a processing banner.

Source maps do not symbolicate frames​

Check:

  • The runtime SDK release matches the source map plugin release.
  • Build output includes source maps.
  • Upload ran in CI and did not skip files.
  • The source map plugin had a valid API token.
  • Uploaded maps appear on the Source maps page.

Laravel events do not appear​

Check:

  • TIDEN_DSN is set in the runtime environment.
  • The installed Laravel bridge version supports your Laravel version.
  • The application is reporting exceptions through Laravel's exception handler.
  • Network egress to the ingest host is allowed.

Agent configuration says it needs an LLM credential​

Create and test a workspace LLM credential. Then edit the agent configuration and select that credential.

Quality gate is blocked​

Open the gate detail and expand blocking components. Common fixes are:

  • Add missing tests.
  • Link tests to specs.
  • Resolve failing tests.
  • Triage production issues.
  • Assign components consistently.
  • Recompute after fixes land.