A publication failed
Preserve successful accounts while diagnosing a failed destination.
A multi-account post can partly succeed. Begin with the per-destination result rather than retrying the whole post.
Recover carefully
-
Open the post detail and identify exactly which account failed.
-
Visit that account on the network to check whether the post appeared despite a timeout or delayed response.
-
Read the error and inspect connection permissions, supported media, required fields and usage limits.
-
Correct the actual cause. Reconnect only the affected account when authorization is the problem.
-
Retry only the confirmed missing destination, then verify its completed result and public post.
Follow-on content
A thread segment or first comment can fail after the main post succeeds. Inspect the chain or comment before retrying; do not create a second main post to solve an unrelated follow-on failure. If the state is uncertain, keep the job identifier and ask support to inspect it before another submission. See Publishing status and recovery for the full state guide.