Account Issues
Troubleshooting guide for Facebook account problems.
Account Troubleshooting
Solutions for common account-related issues.
Error Status
Account showing ERROR status with no specific indicator. This is a general error that means the automated login completed but something prevented the account from operating normally.
Causes
- Account language is not set to English (US)
- Region is not set to United States or date format is not mm/dd/yyyy
- Facebook presented an unexpected page or prompt after login
- The account's session was interrupted during a previous run
- Cookies are stale or corrupted
Diagnosis
- Check that the account's language is set to English (US) on Facebook. This is required for automation to work. Other languages will cause errors even if login succeeds.
- Verify the region is set to United States with mm/dd/yyyy date format
- Check if the account can log in to Facebook at all
- Review the account's activity log for error details
Solutions
- Fix language and region first — if these are wrong, no other fix will help. Log in to Facebook, go to Settings > Language and Region, set language to English (US) and region to United States
- Update credentials — re-enter email and password if they may have changed
- Clear cookies — remove saved cookies and let the system log in fresh
- Reactivate — click Reactivate Account on the account page after fixing the underlying issue
Invalid Credentials
Email or password not accepted by Facebook.
Causes
- Password was changed on Facebook (by you or by Facebook during a security reset)
- Typo in email or password when adding the account
- Account locked by Facebook requiring password reset
Solutions
- Verify the password works by logging in to Facebook directly
- Update the password in MessengerFlow
- If the account is locked, recover it through Facebook first, then update credentials
Invalid 2FA
Two-factor authentication codes are being rejected.
Causes
- Wrong 2FA secret entered — the secret is the text string, not the QR code
- 2FA was disabled or reset on Facebook
- Secret was copied with extra spaces or missing characters
- The 2FA method was changed from authenticator app to SMS
Solutions
- Go to Facebook's 2FA settings and re-copy the secret
- Make sure you're copying the alphanumeric text secret (usually 37-39 characters), not scanning the QR code
- Verify the secret generates valid codes before saving — you can test with any authenticator app
- Update the secret in MessengerFlow
- If 2FA was switched to SMS, re-enable authenticator app method on Facebook
Account Banned
Facebook has suspended or disabled the account.
Indicators
- "Banned" status in MessengerFlow
- Cannot log in to Facebook
- Received a suspension or policy violation notice from Facebook
Actions
- Do not try to recover automated accounts — the appeal process risks linking the account to your real identity
- Remove from MessengerFlow — delete the banned account
- Review what triggered it — check the activity log and recent campaign settings
- Adjust remaining accounts — lower daily limits and review message content
Prevention
- Keep daily volumes under 35 messages per account
- Use proper ramp-up (start low, increase gradually over days)
- Vary message content — avoid sending identical messages
- Include rest days in campaign schedules
- Use aged, established accounts with real profile activity
Rate Limited
Account temporarily restricted from sending messages.
Indicators
rate_limited_untilshows a future date on the account page- Messages stop sending for this account
- Facebook may show in-app warnings about messaging limits
Solutions
- Wait — rate limits expire automatically. The account page shows when the limit lifts
- Clear manually — use the Clear Rate Limit button if you believe the limit has expired but the timer hasn't updated
- Reduce volume — lower the daily message range in campaigns using this account
- Review patterns — high volume, repetitive content, or messaging cold audiences all increase rate limit risk
Prevention
- Stay within recommended daily limits (under 35 messages/day)
- Use natural active hours — don't send messages at 3am
- Include rest days in campaigns
- Spread messages across multiple accounts rather than overloading one
Requires PIN
Facebook is requesting an additional PIN or verification code during login.
Causes
- Facebook enabled extra security on the account (chat PIN, login PIN)
- A suspicious login attempt triggered additional verification
- Account security settings were changed
Solutions
- If you know the PIN, enter it in the account settings in MessengerFlow under the Chat PIN field
- If you don't know the PIN, log in to Facebook directly and check security settings
- You can use a live session with Manual Login to complete the PIN verification interactively
Checkpoint Requests
Facebook is asking to verify your identity before allowing access. This typically appears as a captcha, a "confirm your identity" page, or a request to verify via email/phone.
Causes
- Login from a new IP address or location
- Unusual activity pattern detected
- Facebook's periodic security checks
- Proxy IP changed or was flagged
Solutions
- Start a live session with Manual Login — this lets you complete the checkpoint directly in the browser, and cookies are saved automatically on success
- If using an external browser, complete the verification, export cookies, and update the account in MessengerFlow
Prevention
- Use consistent proxy locations — don't change proxies frequently
- Gradual ramp-up for new accounts
- Avoid sudden changes in messaging volume or patterns
Temporarily Unavailable
Facebook is actively blocking login attempts for this account.
Causes
- Too many login attempts in a short period
- Facebook flagged the IP address or browser fingerprint
- Temporary server-side restriction from Facebook
Solutions
- Wait — these blocks usually lift within 30 minutes to a few hours
- Check your proxy — a flagged or blacklisted proxy IP can trigger this repeatedly
- Try a different proxy — switch to a proxy from a different provider or location
- Don't retry manually — rapid retries extend the block duration. MessengerFlow will retry automatically after the cooldown
Prevention
- Use residential or mobile proxies — datacenter IPs are frequently flagged
- Don't share a single proxy across many accounts
- Let MessengerFlow handle retry timing rather than manually retrying
Unsupported Auth Flow
The account's login requires an authentication step that automated login cannot handle.
Causes
- Facebook requiring phone number verification via SMS
- Security prompts that require human interaction (photo identification, friend recognition)
- Corporate, educational, or managed Facebook accounts with custom auth flows
- Two-factor via SMS only (no authenticator app option)
Solutions
- Start a live session with Manual Login to complete the verification yourself — cookies are saved automatically
- If the auth flow requires adding a phone number or changing security settings, do so on Facebook first, then retry
- If the account consistently requires unsupported verification, it may not be compatible with automated outreach — consider using a different account
Connection Issues
Account failing to connect or timing out during login.
Causes
- Proxy is down, slow, or misconfigured
- Proxy credentials expired or changed
- Network connectivity issues between the server and proxy
- Cookies expired and login is failing silently
Solutions
- Test the proxy — verify it works independently (check the proxy status on the proxy page)
- Clear cookies — remove saved cookies so the system attempts a fresh login
- Try a different proxy — swap to another proxy to rule out proxy-specific issues
- Check proxy credentials — ensure the username, password, IP, and port are correct
