Troubleshooting

Most stops are not crashes. The app is waiting for a fact, a permission, a code, or a model. Find the symptom below and follow the shortest path out.

The queue won't start

Hover the Start applying button. It tells you the blocker in its tooltip. The status line beside it says the same thing in plainer words.

Message or symptom	Fix
“Nothing is waiting in your queue.”	Add a job link on Queue, or add one from Discover.
“Confirm your profile first.”	Go to Profile, review the facts, and tick the confirmation at the bottom.
“Finish setup to start the queue.”	A setup step broke after you finished it. Follow the banner at the top of the window to Fix it.
“Accept the terms to start the queue.”	The terms gate is up. Accept the current terms, or sign in again.
“Update Job Applicator to start the queue.”	The build is too old for the service. Use Check for Updates….
“Couldn't start: …”	A start was attempted and refused. The reason is at the end. A missing model key is the usual one; check Settings → Model connection.
The button is disabled and nothing is obvious.	Look at Needs you. A question or decision may be blocking the whole run.

Profile won't confirm or save

“The profile in Advanced isn't valid JSON yet.” The Advanced section has a syntax error. Fix it there; the rest of the profile cannot save while it is invalid.
The confirmation box is not visible. It is in the save bar at the bottom of the Profile window. Scroll the window, not the section.
“Not saved: …” The worker refused the save. The message says why. Choose Try again after fixing it.
The status says “Kept as a draft”. Nothing is wrong: the facts are saved locally but not confirmed. Tick the confirmation to let applications use them.
Warning: “Fix these so applications fill correctly”. The field it names will fill badly. Open that section and correct it.

A job stopped

Open Needs you; the job is under Check. The reason and buttons depend on why it stopped:

What you see	What to do
Questions to answer	Answer under Questions. Saving re-queues the application automatically.
A decision only you can make	Choose Agree on all applications or Never agree under Decisions. The choice is remembered.
“Continue” for an email code	The app needs a fresh code. Continue runs the application in a visible browser so you can type it.
“Try again”	A temporary failure. It goes back in the queue.
Duplicate	The app believes this job is already in your history. Check History before retrying; there is no retry button for this state.
Closed	The posting is no longer open. Remove it or leave it; it will not run.
Profile unconfirmed	Use Confirm my profile, then start the queue again.
“I applied myself”	You finished it outside the app. This records it as applied and stops retries.

An uncertain result is not proof that nothing was sent If the app lost contact during Submit, check History and the employer's confirmation before trying again. Retrying a submission that may have gone through can create a duplicate application.

A security code is needed

Greenhouse sometimes answers Submit with an emailed code.

With Gmail connected for security codes
The app reads only mail from the ATS that arrived after Submit, finds the code, and enters it. You do not need to do anything. If it cannot find one, the job stops with Continue available.
Without Gmail
A visible browser opens and waits 90 seconds for you to type the code. If nobody does, the job is saved as not submitted and the queue moves on.
To try again
In Needs you, press Continue. It runs the application again in a visible browser for the new code.

If Gmail is connected but codes are not found, use Verify connection in Settings → Mail. The grant may have expired, or the message may come from a mailbox other than the connected one.

Model problems

Symptom	Likely cause and fix
A banner says the queue is waiting for the model	The model stopped answering. The banner says when it will try again. Open Settings to switch or check it.
“Check connection” fails for Ollama	Open Ollama, download a model, and leave the app running. Then check again.
“Check connection” fails for LM Studio	Open LM Studio, load a model, and start its local server. Then check again.
A hosted key is refused	Replace the key in Settings. A saved key is never shown, so a wrong key looks like “saved” until the check fails.
On-device model is unavailable	It needs Apple Silicon and at least 8 GB of memory. The first use downloads a model and runtime; a paused download can be resumed.
Answers are slow	Turn Thinking before answering off. In testing it made answering two to five times slower without answering more questions.

Gmail problems

The connect buttons are disabled. The build is missing its Google OAuth client ID and secret. Settings says so under the buttons. Use the build's support route; this is not something you can fix from the app.
“Google ended the Gmail authorization.” Reconnect. Expired or revoked grants are forgotten on purpose so the app does not keep claiming Gmail works.
“Gmail connection could not be verified.” Check that the Gmail API is enabled for the build's Google project, then reconnect. If you changed Google accounts, connect the intended mailbox.
Mail is connected but replies are not moving. Check Track application status from email is on, and that the model is working. Use Check Email Now in History to see the result immediately.
You want to remove access. Remove it here, or in your Google Account's connected-app settings. Removing the grant here does not delete emails.

Browser problems

The setup browser check fails. Choose Try again. If it keeps failing, quit and relaunch the app, then run the check again.
The browser opens but the page is blank. Wait for the posting to load. If it stays blank, the employer's site may be blocking automation; stop the job and apply manually or try another posting.
The Mac went to sleep. Applications need the Mac awake and the app open. Wake it, then start the queue again. Check the job's state in Needs you first.
You quit while a job was running. The app pauses browser work on quit. Reopen it, check Needs you, and use Try again if the job did not finish.

Getting help

Start with the support page and its safe report template. In the app, Send feedback is at the foot of the sidebar and in the menu bar icon.

Never send credentials or personal application data Do not include passwords, API keys, Gmail tokens, security codes, your résumé, or a real application's answers. A version label and a screenshot of the failing screen with personal details covered is usually enough.

Useful details to include:

The exact screen and the words on the failing button or banner.
Whether the job was a real application or a practice job.
macOS version and the app build from Copy Version Details.
What you expected, what happened, and whether retrying changed it.