Troubleshooting

Go to Autopilot settings and check that autopilot is enabled. The toggle at the top of the page controls whether autopilot is active at all.

Check your Overview for current message usage. If the limit is hit, autopilot pauses until the next billing cycle. Upgrade your plan or wait for the cycle to reset.

If the queue is at 100% capacity, new drafts are paused. Go to the Review page and approve, send, or reject enough drafts to free up space.

Open the fan's drawer on the Fans page and check the "Autopilot enabled" toggle for that fan.

The debounce system waits 8–180 seconds before generating a reply. For very active conversations with rapid messages, the system may cancel an earlier draft and restart the debounce when a newer message arrives. If the fan sends multiple messages in quick succession, only the latest triggers a draft. This is by design — the AI waits until the fan is done typing to generate a single coherent reply.

Also check if there is an existing draft within the last 10 minutes for this fan in the review queue — FanWake won't create a duplicate if one already exists very recently.

FanWake uses an OAuth token to access your Fanvue account. Tokens expire or get revoked. Go to Settings and check your Fanvue connection status. If it shows disconnected, reconnect via the Fanvue OAuth flow.

Approved drafts send within 30 minutes. If more than 30 minutes have passed and the status is still "Scheduled," there may be a Fanvue API connectivity issue. Try using "Send Now" to force an immediate send attempt.

A Failed status means FanWake attempted to send to Fanvue but the request did not succeed. Common causes:

• →Expired or revoked Fanvue access token — reconnect in Settings
• →Fan deleted or blocked — the Fanvue API returns an error for that chat
• →Temporary Fanvue API issue — retry by clicking Send Now

Check that re-engagement is enabled in RE settings.

RE only runs for fans who have been inactive for at least the number of days set in "days before first message." If all your fans messaged you recently, none will qualify until that threshold passes.

Check if RE is disabled for individual fans on the Fans page. Use the filter to find fans who have been inactive and check their RE toggle.

If you have "Max fan age" set to 30 days and fans haven't logged into Fanvue recently, they may not qualify. Try increasing the max age limit or removing it.

If batch size is set to 0 or 1 with a long wait between sends, RE processes very slowly. Check your batch size setting.

A fan who is currently in Attempt 1, 2, or 3 won't receive another RE message until their current cycle completes. This is by design — fans don't get messages from multiple cycles simultaneously.

The most common cause is an incomplete persona. Check:

• →Bio is filled in with specific, vivid detail (not placeholder text)
• →Traits are specific, not generic adjectives
• →Example messages are added (these are the single biggest quality lever)
• →Texting style matches how you actually write

Adjust the message length setting in Persona settings. "Auto" lets the AI decide based on context, which can produce inconsistent lengths. Set it explicitly if you have a preference.

If auto-detect is on, FanWake replies in the language the fan is writing in. If you want all replies in one language, set the response language explicitly in Persona settings.

The strategy controls when pitching happens. Switch to "Warm, then pitch" or "Engagement only" to reduce early pitching. Also ensure the intent gate rule is active in your conversation rules (it is by default).

Check that PPV is enabled in Autopilot settings. Also check the fan's drawer — PPV pitch may be disabled for that specific fan. Ensure you have active PPV templates configured with good descriptions so the AI can assess context.

REPLY_2 has a cooldown — it won't fire if it was used recently for this fan. If it's repeating patterns, the example messages may be too uniform. Add more variety to your example messages in Persona settings.

FanWake autopilot only activates when a fan sends a message. New subscribers who don't message you will never trigger autopilot. Make sure your Fanvue welcome message is compelling enough to get a reply. Consider enabling "Send to empty chats" in RE settings to reach silent subscribers.

No. Fanvue's native automated messages (welcome DMs, scheduled broadcasts) run independently and are not affected by FanWake. They can both be active simultaneously. Fanvue sends its automated messages; FanWake replies when fans respond.