After a failure, can Retry stop creating duplicate messages?
The short answer
Yes. Retry now updates the original failed message instead of repeatedly adding duplicates. Failed-message persistence and ordering are also more stable, reducing misplaced or repeated same-text messages.
Retry updates the original message instead of cloning it
After a failed run, retrying reuses the existing message position where possible so failure → retry → success stays in one coherent place.
Similar messages are less likely to become mixed up
Persistence and ordering for failed messages were refined to reduce duplicates and positioning errors when several messages contain similar text.
Message state is more consistent end to end
Sending, failure, and retry updates now follow a more consistent lifecycle so current and historical views stay aligned.
What's new
Retry updates the original failed message.
Reduced duplicate same-text messages.
Improved failed-message persistence and ordering.
Reduced misplaced similar messages.
Unified message state across send, failure, and retry.
FinchStory 1.0.104–1.0.105 · September 29, 2026