Skip to content
Relay Port

Publishing

Unconfirmed targets

What happens when a platform does not confirm a publish, what evidence you receive, and how to settle the target yourself.

Sometimes a platform receives a publish call but its answer never arrives or does not say what happened: a timeout, a dropped connection, an error after the post may already be live. Sending the call again could publish the post twice, so Relay Port does not send it again. It reconciles instead: it reads the platform to find out what happened.

  • If the reads find the post, the target becomes published.
  • If they show that nothing went live, the target becomes failed, and a retry is safe.
  • If they cannot tell, the target becomes unconfirmed.

What you receive

  • The post.target.unconfirmed event, if you have a webhook endpoint.
  • On the target, from GET /posts/{id}: status: "unconfirmed", an error whose evidence lists what was checked and what each check returned, and the reconciliation record.
  • The steps in the target's timeline, GET /posts/{id}/events.

A post whose targets are all unconfirmed has the status unconfirmed. It is never reported as failed, because the post may be live.

Settle it

  1. Open the account on the platform and look for the post.
  2. If it is there, call POST /posts/{id}/targets/{targetId}/resolve with outcome: "published" and its permalink when you have it. If it is not, resolve it with outcome: "failed".
  3. To send a post that did not go out, call POST /posts/{id}/retry with includeUnconfirmed: true. Do this only after checking, because without the check a retry may publish a second copy.

The post.target.resolved event fires when a target is settled. Use a sandbox post with outcome: "unconfirmed" to test this path before it happens for real.