Troubleshooting
Resolve a failed or uncertain publishing attempt
Distinguish a definite rejection from an uncertain provider result and avoid accidentally publishing the same content twice.
/calendarOpen this screen →Identify the result
- Published means the provider confirmed delivery and RunFloor stored the result.
- Failed means RunFloor received a definite rejection before a successful provider result.
- Needs attention can indicate a connection, media, timing, or provider problem that requires review.
- Uncertain means the provider may have accepted the post but RunFloor did not receive a trustworthy final answer.
Handle an uncertain result safely
- 1
Do not retry immediately
An uncertain result may already be public. Automatic retry is intentionally blocked to prevent duplicates.
- 2
Check the destination directly
Open the exact Page, account, board, profile, or Company Page and look for the complete post and media.
- 3
Record what you find
If the post exists, treat it as delivered and do not recreate it. If it is absent after the provider has had time to process, prepare a new reviewed version rather than resubmitting the uncertain claim.
- 4
Contact support when evidence conflicts
Provide the platform, destination name, approximate time, and visible RunFloor status. Never send credentials or access tokens.
Handle a definite failure
- 1
Read the safe error message
Determine whether the problem is the connection, media, caption, destination, schedule, or provider availability.
- 2
Correct the cause
Reconnect an expired account, replace unsupported media, revise invalid content, or choose a valid future time.
- 3
Review a new attempt
Open the corrected saved version, approve it again when required, and use only the retry action explicitly offered by RunFloor.
What success looks like
You have confirmed the real provider result, avoided a duplicate post, corrected any definite failure, and the Calendar no longer contains an unexplained item requiring attention.
Troubleshooting
Common problems
The provider shows the post but RunFloor says uncertain.
Do not retry. Preserve the RunFloor record and contact support with the provider post link so the audit result can be reviewed safely.
The provider does not show the post.
Allow for provider processing, refresh the destination, and then create a new reviewed version if the original remains absent. Do not reuse an uncertain submission blindly.
The same failure keeps returning.
Stop repeated attempts and review the saved connection, format, media, and destination requirements before contacting support.