Troubleshooting

”An agent run got stuck — Stop is disabled”

Loomcycle restarted while your run was mid-flight. The local row still says running but loomcycle lost the cancel registry. The heartbeat sweeper marks it failed within a few minutes; you can re-run the agent then.

”I generated a CV but it’s empty / generic”

Three usual causes, in order:

  1. Stage 2 wasn’t run for the application’s company. The cv-adapter falls back to generic bullets when the employer profile is missing. Re-run Stage 2 on that posting and re-generate.
  2. Your CV template is empty or has only headings. The cv-adapter only re-orders existing material; it doesn’t invent. Open Settings → CV Templates and check the active row has actual experience bullets.
  3. The agent’s prompt was clobbered by an injection in the job description. Look in injection_incidents for a row with the application’s source ref — if there is one, the description bypassed the safety filter.

”I switched to ATS mode but Stage 4 still renders Inter”

Two layers must agree: the Stage 3 generation has to know it was ATS (the cv-adapter rewrites bullet structure), and Stage 4 has to render in Calibri 11pt. If you switched after generation, the CV body is still in standard-mode shape; click Re-Generate on the row first.

”The job-searcher returned no results”

Check Settings → Profile target role + work preferences. The agent filters at source — too narrow a query (e.g., “Senior Backend Engineer in Vatican City, full-time only”) may legitimately return zero. Loosen one preference at a time.

”I deleted my account but I still receive emails”

You shouldn’t — the cascade deletes notification subscriptions. If you do, write to [email protected] with the date you deleted and we’ll trace it. The account_deletions audit row gives ops a way to verify the deletion fired.

”The Chrome extension isn’t logging me in”

Browser extensions are a separate auth path (Bearer tokens generated at Settings → API Tokens). Re-mint a token, paste it into the extension’s settings, and reload.

Either: a) the legal docs were materially updated (the version bumped) — you’ll see the previously-accepted box pre-ticked and only the new doc requires a fresh acceptance; or b) your user_settings.accepted_*_version somehow ended up null. The route’s gate detects it and redirects; one accept click fixes it.

Anything else

Floating Help chat (bottom-right) handles most procedural questions. For an actual bug, /feedback is the direct channel — it’s read by the dev team daily.