Guide
Troubleshoot common issues
Work through the practical checks that usually unblock setup, apply, and outreach workflows.
When something fails, isolate one workflow at a time and test the smallest reproducible case first. A single-job test is usually more useful than retrying a full batch immediately.
First checks
Confirm login and email verification
Make sure the extension is using the expected account and the email is verified.
Confirm plan or trial access
Some workflows require paid feature access after trial usage is exhausted.
Confirm the provider and model
Check that the selected provider and model match the key you intend to use.
Confirm the API key is saved
If the key was removed or changed, AI features can fail immediately.
Confirm billing or credits
Provider-side 402, balance, or billing issues can block generation.
Refresh the target page after settings changes
Refresh LinkedIn, Indeed, Gmail, or the ATS page so new settings are loaded.
Reopen the extension panel
A stale panel can miss updated page context.
Test a single job first
Do not retry a full list or search run before a one-job test looks healthy.
Check whether job details loaded
If the title, company, or description is missing, later AI steps can degrade.
Review console or exported logs if available
Use the best diagnostic data the product exposes before reporting the issue.
Common problems to check
- Job context did not load correctly.
- AI provider or key error.
- Provider quota or balance exhausted.
- The current page is outside supported workflows.
- Autofill missed a field because of structure or widget limitations.
- A bot run stopped because of page state, limits, or a validation failure.
- CAPTCHA blocked completion.
- Resume upload or attachment handling failed.
- Settings changed but the old behavior stayed cached on the page.
- Gmail or outreach flow failed.
- LinkedIn showed a warning, checkpoint, or restriction.
info
Refresh reminder
After changing extension settings, refresh the relevant LinkedIn, Indeed, Gmail, or ATS page so the updated settings are loaded.
What to include in a support request
Include the feature or workflow name, the website you were using, what you expected, what actually happened, a screenshot, any console or exported logs you have, whether it repeats, and your account email if appropriate. We aim to respond as soon as possible.