Recover from an uncertain publishing request
A network timeout can leave the sender unsure whether a public post exists. Handle that uncertainty before retrying.
Context and provenance
Save the exact approved draft ID and inspect its recorded publishing state. A completed result has a provider post ID. An uncertain result means the connection failed after the request may have reached the platform. Treat the two states differently: an absent success response is not proof that nothing was published.
Check the authorized account for the exact text and record any matching post ID. The owner reconciliation command checks the account and text before marking an uncertain attempt as completed. Do not repeatedly press a send control or automatically clear the stored attempt. A second request may create a second public post and make the editorial record harder to follow.
If no post can be identified, preserve the evidence of the request and investigate before deciding on another attempt. This edition intentionally blocks blind retry of uncertain posts. Its connector does not implement automatic replies, direct messages or engagement campaigns. Platform access and automation requirements still apply to whatever workflow the operator builds around it.
Sources and evidence
Editorial review: 2026-09-23. New evidence may change this account.