Troubleshooting

Every error in the app and the API names a request id (req_…). Quote it when you write to info@weharness.io. For coding tools, see MCP limits and troubleshooting.

Problem	What to do
Forgot your password	Select Forgot Password? on the sign-in page. The link works for 30 minutes.
The set-password link expired	It works for 72 hours. Write to info@weharness.io for a new one.
“The account is paused” after failed attempts	After 10 failed sign-ins the account is paused for a while. Wait, or reset your password.
Lost your phone (two-step sign-in)	Sign in with a recovery code, then set up a new authenticator. Without recovery codes, write to info@weharness.io from your account’s address. See Getting access.
Signed out unexpectedly	The web app signs you out after 2 hours without activity and 12 hours after sign-in. Sign out everywhere on another device also signs you out here.

Invitations

Problem	What to do
“This invitation is not valid for your account”	Sign in with the email address the invitation was sent to. The invitation may also have expired (7 days), been used, or been withdrawn.
“Verify your email address first”	Open the verification link WeHarness sign-in sent you, then open the invitation again.
Your colleague has no account	Accounts are made by WeHarness during the pilot. See Join another workspace.

Problem	What to do
Installation requested	An owner of the GitHub organization has to approve the app on GitHub.
A repository is missing	Select Choose repositories beside the account in Integrations and add it on GitHub, then refresh.
“That GitHub installation is already connected to another workspace”	An installation belongs to one workspace. Disconnect it there first, or install the app on another account.
Only owners and admins can connect GitHub	Ask an owner or admin of your workspace.
A push that adds or changes a CI file fails	Changing CI files needs the app’s Workflows permission, which the account that installed the app accepts on GitHub.

Problem	What to do
WeHarness is busy above the message box	WeHarness’s queue is behind. Your message waits or is refused with a time to try again; work already accepted finishes.
`429 WORKSPACE_BUSY`, `503 AT_CAPACITY`, `503 PROVIDER_BUSY`	Too much work is running. Try again in a minute; you can also pick another model for `PROVIDER_BUSY`.
This message reached its credit cap	One message may use up to 100 credits (or your per-run budget). Ask for a smaller step, or continue in a new message.
The model shows coming soon	It is not offered right now. Choose another model; WeHarness never switches it for you. See Models.
“Your … key was refused”	The provider refused your own model key. Switch the session to WeHarness credits, or have an owner or admin replace the key. See Model keys.
A file shows Not read	The reason is shown beside it, for example a secret in the file or an unsupported format.

Problem	What to do
Approve plan is not shown	Only owners and admins approve plans.
“The quote for this plan has expired”	A plan’s quote lasts 7 days. Plan again to get a new one.
Approval refused: a newer version exists, or the code changed	Approve the newest version. If the session now reads another branch or commit, plan again.
“Approved by a signed-in person in the WeHarness web app”	Approvals happen only in the web app, never through the API with a token or over MCP.

Problem	What to do
The push asks for approval again	The draft changed after the approval. An approval covers only the exact changes it showed.
No push for an uploaded project	Only a session whose code comes from GitHub can push. Download the Patch from Changes.
CI checks do not show	WeHarness watches a pull request’s checks for up to 30 minutes. Type `/checks` to read them again.

Problem	What to do
A command waits for a sandbox	One sandbox works for you at a time, and a workspace runs at most two for people’s work during the pilot. It starts when one is free.
A clean check is inconclusive	Some evidence was not recorded. Missing evidence never counts as passed. Check the Checks tab for what is missing.
“Not verified” on a task	Two reproductions in a row failed. A person can choose Allow 2 more attempts in the app. See Working on an approved plan.
A preview stopped	A preview runs for 30 minutes at most. Ask again to start a new one.

Problem	What to do
`402 OUT_OF_CREDITS`	The workspace has no credits for new work. Running work finishes. Write to info@weharness.io.
`402 MEMBER_BUDGET_REACHED`	Your monthly budget is used. Ask an owner or admin to change it in Usage & billing.
`402 RUN_BUDGET`	The work would reserve more than your per-run budget. Ask an owner or admin.
`423 WORK_PAUSED` or `WORKSPACE_PAUSED`	New work is paused, by an automatic safety measure or by WeHarness. Running work finishes. Write to info@weharness.io, with the reason code if the message has one.

Check the key. The error Send a WeHarness ingest key means no key reached the gateway. The header is Authorization: Bearer whk_…; in OTEL_EXPORTER_OTLP_TRACES_HEADERS the space is written %20. A revoked key is refused.
Check the endpoint. It is https://api.weharness.io/otlp/v1/traces, OTLP over HTTP. gRPC is not accepted.
Flush before exit. A short script must call shutdown() (SDK) or provider.shutdown() (OpenTelemetry), or its last spans are never sent.
Check the times. Spans more than 7 days in the past or an hour in the future are refused. Check your machine’s clock.
Look at what arrived. Setup shows accepted, stored, refused and deferred spans per key for the last 24 hours. Deferred spans are retried by your exporter.
Check the environment. Tracing shows one environment at a time. Choose the key’s environment at the top.

A trace shows no prompts or outputs? Only metadata is kept unless the key keeps content and your SDK sends it. See Content capture.

Write to info@weharness.io with what you did, what you expected, and the request id.