Why did my post not crosspost?

1. Confirm the automation and direction

Open Automations and find the relevant Auto Cross-post entry. Check From, To and whether it is active. A connection between two accounts does not create an automation by itself.

Review the last-run information. If the automation is paused, activate it only when you are ready for new posts to be copied. If the last run is older than expected, note that time for support.

2. Allow for the checking interval

Crossposting is checked periodically, according to your plan. A post published just after a check may need to wait for a later cycle.

Use a new post published after activation when testing setup. Avoid repeatedly disconnecting accounts or recreating the automation while waiting; that makes the sequence harder to investigate.

3. Check exclusions and the post format

Look for #nocrosspost or #keephere in the source post. These deliberately keep a post from crossposting. Check whether your test is an original post, a reply, a repost or a quote post.

For a quote post, review the Crosspost quote posts option. For long text, threads and media, the destination's format requirements also matter. A successful plain-text test does not establish support for every attachment.

• Confirm that you published on the exact account selected as the source.
• Check the quote-post setting if the source includes a quoted post.
• Compare the supported formats on the source and destination networks.
• Remember that an edit to an already-published source is not a new-post test.

4. Check connections and account access

Open Connect Accounts and check that both accounts are connected. If authorization has expired or the network asks you to reconnect, complete that step and verify the selected accounts in your automation.

Check your subscription or trial status and automation allowances. Do not assume a missed post will automatically be retried after changing a connection; verify the destination before taking any further publishing action.

5. Send the details needed to investigate

If the post is still missing, contact support with the source URL, both network names, the relevant account names, the publication time and timezone, and the automation's last-run time.

Include any visible error text and whether a plain-text post has worked before. Do not send passwords, access tokens or private account credentials.

• Before manually publishing a replacement, check that a copy has not appeared.
• Pause the relevant automation if you need to prevent it from acting while you investigate.
• Describe what you expected and what you can see on the destination.