Skip to content
docs Search these pages /

When an extension save fails

The save outcomes the ATSReady extension side panel reports, where a timed-out import shows up instead, and what to do about each one.

Chrome extension · about 2 minutes

On this page
  1. What the panel shows
  2. Two outcomes that look like something else
  3. What to do next
  4. Related

The side panel's save control has one state at a time, and only four of them are outcomes you act on: saved, already on your board, could not be read, and monthly limit reached.

What the panel shows

The save control reports the outcome in two places at once — a button label, and for most outcomes a banner above it. They do not use the same words, so both are listed here.

Outcome Button reads Banner reads
Accepted, now processing Saved to your board Saved to ATSReady
Already saved Already saved Already on your board
The page could not be read Try again Could not save this job
Monthly import limit reached Limit reached no banner

The monthly limit is the one outcome with no banner. It replaces the surrounding panel content instead, under the label Monthly limit reached, with your usage for the month and the date your imports come back. Monthly job import allowance is the page that owns the counter, and Why something is locked tells a spent allowance apart from a plan that never included one.

Two outcomes that look like something else

  • Expired sign-in is not a separate outcome. If your extension session is no longer authenticated, the save is refused and the panel reports it under Could not save this job, the same title a page-read failure uses. If that title appears on a page that reads perfectly well, check whether you are still signed in — see Sign in to the extension.
  • A slow import does not fail in the panel. Nothing here times out. The save is accepted, the background worker polls for the result, and if that poll runs past its window the entry turns to Failed on the Recently saved list instead. The panel may have already said the job was saved by then, because it was — the import is what did not finish.

What to do next

  • Reload the job page and try again after a read failure.
  • Sign in again from the panel if extension authentication expired.
  • Use Add a job to ATSReady if the page is too hard for the extension to read.
  • Check monthly job import allowance if quota is the blocker.
  • Open the Activity log for a save that was accepted but shows as failed afterwards.