Troubleshooting
Reconnect an expired social account
Restore provider authorization for the correct company and review affected scheduled work before publishing again.
/studio/facebookOpen this screen →Reconnect the provider
- 1
Open Integrations
Confirm the Company workspace before changing any connection.
- 2
Choose the affected provider
Use its Connect or reconnect action. Sign in with the provider account that controls the intended destination.
- 3
Review permissions
Approve the required publishing and discovery permissions. Do not paste tokens, codes, or passwords into RunFloor support messages.
- 4
Select the real destination
Choose only the Page, professional account, board, member profile, or Company Page that belongs to this workspace.
- 5
Return and verify
Confirm RunFloor shows the expected account name, identifier, connected status, and destination choices.
Review affected content
- 1
Open Calendar
Filter for items that need attention and review work associated with the expired connection.
- 2
Check each destination
Confirm that the reconnected account matches the destination saved with the post.
- 3
Retry only definite failures
Use a RunFloor retry action only when the prior attempt definitely failed. Check the provider first when the earlier outcome is uncertain.
What success looks like
Integrations shows the correct destination as connected, it appears in supported creation and publishing screens, and affected posts can be reviewed without an authorization warning.
Troubleshooting
Common problems
The account reconnects but the destination is missing.
Confirm the provider login has management access and that every required permission and destination was selected during authorization.
The wrong company received the connection.
Disconnect it from the incorrect workspace, select the intended company, and start authorization again.
Scheduled items still need attention.
Refresh Calendar and inspect each item. Reconnection does not automatically retry or rewrite preserved publishing records.