Scores or documents are missing
Two different things go wrong here. Fit scores come from a pass that runs on its own; documents come from a button you press. Work out which you are missing first.
No fit scores
Scoring needs an active profile: with no CV imported there is nothing to score against, and the pass stops before it starts. Import your CV if you have not.
Past that, two conditions pause scoring rather than fail it.
- Not enough credit. A call is refused unless the balance covers the worst case it might cost, so scoring stops while there is still money on the account rather than at exactly zero. Nothing is charged, and every unscored job re-enters the queue next run.
- The provider is rate limiting. Same behaviour — the rest of the batch is deferred and picked up next time round.
Neither puts a message on Suggestions. The jobs simply sit there unscored, which is why this is easy to misread as a fault. To see it, check the Discovery card on Overview: total jobs well ahead of scored, and staying there.
Your balance is at the top of the Billing page. Read the number rather than waiting for the warning line beneath it — that only appears at zero, and scoring will have stopped before then.
No documents
Drafting says what it is doing, so read the card rather than guessing.
Waiting followed by a reason is a condition, not a failure — short of credit, or rate limited. The application stays queued and finishes by itself once that clears. Prepare failed followed by a reason is a real failure.
Where you are standing decides what you can do. On Suggestions and Jobs a failed draft offers Retry beside the message. On the pipeline board the card states the failure but carries no retry button, so go to Suggestions or Jobs to ask again.
If neither message shows, nothing was ever asked for. Drafting starts only when you press for it — Prepare application, or Process anyway — generate CV & cover letter on a flagged or low-scoring job. See generating a tailored CV and cover letter.
If you are using your own API key
A key is checked against the provider the moment you save it, so a bad one is refused there and then. A key that worked and then stopped is a different problem: usually it was revoked at the provider, or the account behind it has run out of quota or has no billing set up. Check that account first — Rolehound cannot see any of it.
If anywhere in the app tells you your stored key could not be read, paste it in again on the Billing page. That message comes from the work itself, not from Billing, so it turns up wherever the call was made. Clearing the key puts you back on Rolehound's own metered credit while you sort it out. Using your own API key covers both.