Scheduled threads post out of order after a retry
33% of problems resolved · median first response 11h
When the first post of a thread fails and retries, the remaining posts publish before the retry lands, so the thread reads backwards. Reproduced on three accounts.
Environment
Web · Chrome 141
Response timeline
Every state change is public, including the company's reasoning.
Reported
Jun 2, 2026Sam Oduya reported this problem as a verified user.
Acknowledged — Ada Meyer
Jun 2, 2026Reproduced on our side. The retry path re-enters the queue at the tail instead of holding thread order.
Investigating — Ada Meyer
Jun 4, 2026Tracing the publish worker. Thread ordering is not persisted across retries.
Fix planned — Ada Meyer
Jun 8, 2026Fix scheduled for the 14 June release. Threads will hold a sequence lock through retries.
Resolved — Ada Meyer
Jun 14, 2026Shipped in 3.9.0. Retries now preserve thread sequence.
Confirmed by an affected user
Jun 16, 2026Confirmed across all three accounts over two days of posting. Order is correct.
Linked release
The fix, tied back to the problem it closes.
Thread ordering survives retries
Jun 14, 2026Publishing threads now hold a sequence lock across retries, so a failed first post no longer reorders the thread.
Other Postloop problems
Analytics export omits the last day of the range
Selecting 1–31 August exports through the 30th. Off-by-one in the range boundary.
Editor role cannot reschedule a post they created
An editor can create and submit a post but cannot move it once it is approved, which forces an admin into every small timing change.
Bulk CSV import silently drops rows over 280 characters
Importing a 400-row CSV produced 361 scheduled posts with no error. The dropped rows were all long-form LinkedIn copy.
Instagram carousel previews show the wrong crop
The preview applies a 1:1 crop even when the post is set to 4:5, so approvers sign off on a framing that is not what publishes.