The platform signed Melon out, so that account has stopped syncing. Click Reconnect on the account's row in Settings → Integrations and sign in again. Nothing is lost — data resumes from where it stopped, and the split keeps its history.

This is the most common integration issue, and it is not a sign anything is broken.

Platform sessions expire on their own. They are not permanent API keys — Melon holds a session the same way a browser does, and platforms end those sessions on their own schedule. SextPanther does this most often.

Some sessions die quietly: the account still says connected but no new data arrives. So Melon checks for accounts that look connected but have produced no daily earnings for three or more days while attached to an active earnings split, and flags those as needing reauthentication.

A flagged account stops being retried automatically. This is deliberate — repeatedly hammering a dead session gets the account rate-limited or locked. It waits for a real sign-in.

The Melon Split column on the accounts table shows which split each account feeds, so you can tell at a glance whether a flagged account is one that matters.

Earnings splits stop accruing while the account is disconnected. The days with no data stay empty until the account is reconnected and backfilled — they do not fill themselves in retroactively from a later sync.

If a split was disconnected across a billing boundary, check the balance before the next charge. The charge will only reflect the days that actually synced.

Cashout splits that rely on bank-deposit detection are unaffected, because they read the creator's bank rather than the platform.

A connection that drops again within hours usually means the credentials changed, or the creator enabled a login protection that the connection cannot pass. Confirm the login works in a normal browser first, then reconnect.