Skip to content

When the outcome is unknown

What to do when a platform didn't confirm whether a post went out, why retry stays off for a while, and what "Confirmed not posted" means.

Updated 2 min read
On this page
  1. "Outcome unknown"
  2. "Confirmed not posted"
  3. You can see the post on the platform
  4. Why this happens

Sometimes a platform receives a post but doesn't answer clearly, so nobody knows yet whether it went out. Trabbly handles this carefully so a post is never published twice. Everyone can read the status; checking, retrying and marking as published need an owner, admin, brand manager or publisher.

"Outcome unknown"

The explanation reads: the platform "didn't confirm whether the post went out, so it may already be live. Trabbly is checking the account and allows a retry only once it knows the post isn't there. You don't need to do anything yet."

What happens next:

  1. Retry now stays off: "Retrying now could post twice, so retry stays off until Trabbly has checked the account. It checks automatically every few minutes."
  2. Trabbly looks for the post on the account.
  3. If it finds it, the post is marked published with its link: "Found it: the post is live".
  4. If it is sure the post isn't there, the status changes to Confirmed not posted (below).

"Confirmed not posted"

The explanation reads: "Trabbly checked the account and the post isn't there, so nothing was published. You can retry safely." Select Retry now.

You can see the post on the platform

If you can see the post live but Trabbly hasn't found it yet, use Mark as published, paste the post's full link (starting with https://) and confirm. The post is then recorded as published by hand.

Why this happens

The connection dropped after the platform received the post, the platform answered with an error after accepting it, or processing (often video) took longer than expected. None of these mean you did anything wrong.

Was this article helpful?

Ask a question