Setup
Limits And Safety
Learn how GrowthEngene uses LinkedIn pacing, email pacing, domain pacing, auto-send guards, and pause conditions.
Quick Answer
Why Limits Matter
Limits protect account quality, sender reputation, data quality, and user control. They also make automation behavior easier to predict.
GrowthEngene has several kinds of limits: LinkedIn account limits, warmup limits, human schedule windows, email sending limits, recipient-domain pacing, verification caps, provider caps, monthly search budgets, and credit availability.
- LinkedIn action pacing.
- Email sending pacing.
- Recipient domain pacing.
- Provider and monthly caps.
- Auto-send guard requirements.
Common Pause Conditions
GrowthEngene may pause when a required check fails or configured limits are reached. Pauses should be treated as safety signals, not just errors.
A clear pause reason is better than silent automation. Users should be able to see whether the issue is account health, sender setup, recipient quality, review state, schedule timing, credits, or runtime health.
- LinkedIn session needs attention.
- Sender email is not verified.
- Recipient email is invalid or low confidence.
- Suppression or unsubscribe rule blocks sending.
- Daily, hourly, or domain pacing limit is reached.
LinkedIn Safety Controls
LinkedIn safety controls are account-aware. The system can evaluate account type, daily invites, weekly invites, messages, profile opens, monthly search budget, pending invites, acceptance rate, cooldowns, warmup state, and human schedule.
- Free, premium, Sales Navigator, and Recruiter Lite accounts can use different internal limits.
- Pending invite volume can move from clear to warning, throttled, or blocked.
- Low acceptance rate can throttle or block invite activity.
- Warmup can allow discovery before connection or message actions.
- Human schedule and quiet days can block activity outside configured windows.
Outreach Send Guards
Outreach send guards control whether GrowthEngene may send without review. They apply differently depending on send mode and channel.
- draft_only creates drafts and never sends.
- review_first requires approval before sending.
- auto_send_guarded requires score, confidence, sender, recipient, resume, suppression, and pacing checks.
- auto_send still requires hard checks such as valid recipient, sender, suppression, resume, and pacing where configured.
- LinkedIn job outreach can require verified email; LinkedIn post outreach can require direct email unless after-discovery auto-send is intentionally enabled.
Email And Domain Pacing
Email sending and email verification both need pacing. Same-recipient-domain controls help prevent too many actions against one domain in a short period.
- SMTP probing has per-minute, per-hour, per-day, per-domain, and source-IP style controls where configured.
- Outreach sending can enforce minimum delay and maximum sends per recipient domain.
- Transactional, warmup, outreach, and verification streams should not be treated as the same traffic.
- Domain pacing blocks are expected and should be retried later instead of bypassed.
How To Increase Volume Safely
Increase one dimension at a time. A workflow that performs well at small volume should be observed before adding more sources, more schedules, more accounts, or more auto-send permissions.
- Start with manual runs before recurring schedules.
- Use review-first before guarded auto-send.
- Raise source limits gradually.
- Watch skipped, blocked, failed, and review states.
- Reduce volume when reply quality, bounces, account resistance, or safety warnings degrade.
Frequently Asked Questions
Why does GrowthEngene pause automation?
GrowthEngene pauses automation when configured limits are reached, required safety checks fail, or a session/account needs manual attention.
Are credits the same as safety limits?
No. Credits control whether the workspace has enough allowance to run work. Safety limits control whether the account, sender, domain, provider, or workflow should act now.
When should I enable auto-send?
Enable guarded auto-send only after targeting quality, sender setup, recipient confidence, resume handling, suppression checks, and pacing behavior are proven in review-first mode.