OAuth and channel connect errors
Connecting a channel is a handshake between three parties — your browser, the platform and UseNadia — and any one of them can break it. Most of what goes wrong is on this page, roughly in the order you are likely to meet it.
A red dot on the channel, “Channel disconnected”
Section titled “A red dot on the channel, “Channel disconnected””The most common situation, and not an error of yours. A red dot on a channel’s avatar in the account switcher means the channel needs attention: its access token has expired, Meta or TikTok revoked it (a password change, a permission declined, the app removed from the account), or a setup step was never finished. Its posts fail until you act.
Open the account switcher, Manage brands & channels, and in the Channels section the channel reads Channel disconnected with a Reconnect button. Reconnect re-runs the platform’s authorisation; do it as the same account, or the channel’s history ends up describing someone else. Posts that already failed are not retried: reschedule them. The details are on Manage a channel.
Meta asks for a step after the redirect
Section titled “Meta asks for a step after the redirect”Meta sometimes needs a follow-up before the channel is usable — a choice to
make, a permission to confirm. UseNadia brings you back with a ?continue=
parameter and replays that step; until you finish it the channel sits in the
switcher with its red dot. Finish it from the screen UseNadia shows, or click
Reconnect to start again. See
Connect a channel.
“Please refresh the channel that needs to be refreshed”
Section titled ““Please refresh the channel that needs to be refreshed””You clicked Reconnect on a channel and authorised a different account on the platform’s screen. UseNadia refuses rather than silently swapping the two: a channel’s posts, people and collected history belong to one account. Start Reconnect again and sign in to the platform as the account the channel was created with.
“This social channel was connected previously to another UseNadia account”
Section titled ““This social channel was connected previously to another UseNadia account””The warning behind a ?precondition= return. It belongs to the original
project’s billing — it is raised for a trial workspace that connects a channel
another workspace already had — and billing is off on app.usenadia.com, so you
should never see it. If you do, write to
hello@usenadia.com.
“Invalid state” / “Invalid or expired state”
Section titled ““Invalid state” / “Invalid or expired state””You see it as a flash message after the platform redirects back.
What it means: UseNadia generates a one-time token when you start the connect flow and expects the platform to return it. A mismatch — the flow was started in one tab and finished in another, the authorisation page was refreshed or bookmarked, too long passed — produces this error.
Fix: start again from Add Channel, in one tab, in one go. If a privacy
extension or a very strict cookie setting drops the session between the
redirect out and the redirect back, allow app.usenadia.com for the duration
of the connect.
“invalid_grant”
Section titled ““invalid_grant””The code the platform handed back was rejected when UseNadia tried to exchange it for a token — usually because it was used twice (a double click, a retry) or expired (platforms give about a minute).
Fix: start the connect flow over; codes cannot be reused. If a fresh attempt fails the same way, write to hello@usenadia.com with the time of the attempt.
“Failed to fetch” / “fetch failed”
Section titled ““Failed to fetch” / “fetch failed””UseNadia tried to talk to the platform’s API and the request failed at the network level. Retry once: if it succeeds, the platform had a blip. If it keeps failing, write to hello@usenadia.com with the time of the attempt.