Help
Troubleshooting GrowthEngene
Resolve common GrowthEngene issues with LinkedIn sessions, email sending, discovery, campaigns, workers, and automation pauses.
Quick Answer
Common Issues To Check First
When a workflow does not run as expected, start with the dependencies that most often pause automation.
Most GrowthEngene issues can be narrowed by asking which layer failed: setup readiness, source capture, enrichment, email discovery, review state, sender policy, schedule dispatch, worker runtime, or credits.
- LinkedIn session expired or requires attention.
- Sender email is not verified.
- Recipient email did not pass checks.
- Daily or hourly limits were reached.
- Campaign requires review before sending.
- Worker or scheduler health needs attention.
How To Resolve Faster
Use the relevant module page to narrow the issue. For example, email failures usually belong in email setup or email discovery, while job discovery issues usually begin with LinkedIn session and search settings.
- If nothing starts, check scheduler, account selection, credits, and launch blockers.
- If browser work starts but no rows appear, check source URL, session health, worker logs, and capture limits.
- If rows appear but no people are found, check company identity, role filters, and Search Intelligence fallback.
- If people appear but no emails are found, check discovery provider, company domain, confidence policy, and verification queue.
- If emails exist but nothing sends, check sender, resume, suppression, pacing, and send mode.
Workflow-Specific Symptoms
Different GrowthEngene workflows fail in different ways. Use the symptom to jump to the right setup area instead of changing unrelated settings.
- LinkedIn Jobs: preset missing, search type mismatch, no linked pipeline, no people found, low relevance, missing resume.
- LinkedIn Posts: source inactive, classifier disabled, no direct contact, no resume profile, review required, no sender.
- Campaigns: no contacts, sender not allowed, follow-up timing not reached, suppression, reply stopped sequence.
- Email Discovery: missing name/domain, provider cap, catch-all ambiguity, low confidence, verification queue disabled.
- Pipelines: incompatible type, missing required step, low confidence, blocked send posture, failed upstream context.
Operational Checks
Operators and admins should also check runtime health. The system includes API, scheduler, worker, browser/CDP, Redis, MySQL, MinIO, email workers, and verification workers depending on deployment.
- API health and GraphQL availability.
- Scheduler health and schedule paused/next-run state.
- Worker readiness and browser capacity.
- Redis and queue connectivity.
- Database and storage availability.
- Email send worker and verification worker keys where those queues are used.
When To Contact Support
Contact support when the UI does not show a clear reason, when credit reservations appear stuck, when a worker repeatedly fails the same workflow, or when sender/session state looks correct but automation still cannot proceed.
- Include workspace, workflow, account, run, schedule, campaign, or pipeline identifiers where available.
- Include the blocked reason or latest visible error.
- Mention whether the problem affects all workflows or one specific source.
- Avoid sharing raw passwords, secrets, or private API keys in support messages.
Frequently Asked Questions
Where should I start when automation stops?
Check session status, safety limits, sender verification, campaign review state, and worker or scheduler health.
Why did a workflow create data but not send anything?
The workflow may be in draft-only or review-first mode, or it may be blocked by sender, recipient, resume, suppression, domain pacing, score, confidence, or credit checks.
What should I check if a schedule does not run?
Check whether the schedule is paused, the scheduler is healthy, the selected account session is active, credits are available, and account safety limits allow the run.