[Fix] Suggested tasks do not appear in Teams and Telegram automation reports - #1757
Merged
Merged
Conversation
Contributor
![roomote-community[bot]](https://avatars.githubusercontent.com/u/211522643?s=60&v=4){kind=small}
Contributor
Author
|
Fixed the retry-safety gap in c8c53b98. Teams and Telegram now reserve a durable tracked-card claim before posting, so an uncertain provider outcome or failed post-send finalization cannot cause a duplicate card on retry. Focused SDK tests, type checking, formatting, oxlint, and the full pre-push suite passed. |
mrubens
marked this pull request as ready for review
August 27, 2026 23:55
mrubens
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
August 27, 2026 23:55
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Fast automation closeouts now accept structured suggested tasks on Teams and Telegram, deliver a tracked card for each suggestion, and preserve the existing launch routing. Teams suggestions can be launched with a reaction, while Telegram suggestions include a Start button.
The automation prompt and delivery guard now describe all supported chat surfaces. The Teams adapter handles both editable-root and new-message report paths, and the Telegram adapter posts its suggestion cards beneath the report. Teams and Telegram reserve a durable tracked-card claim before contacting the provider, then finalize that claim with the accepted message ID so retries cannot post duplicate launch cards when the provider outcome or post-send tracking is interrupted.
Why this change was made
The original implementation allowed structured suggestions only for Slack and Discord. Teams and Telegram automation reports could otherwise be delivered, but their closeouts were rejected before the parent adapters could post them, leaving users without the report or launchable follow-ups.
This addresses the review feedback on PR #1755, specifically discussion_r3876625249.
Impact
Teams and Telegram users can now receive and launch suggested tasks from Fast automation reports with the same persisted work-item and tracked-card lifecycle used by the existing chat integrations. Focused service, adapter, and database-backed tests cover the supported surfaces, delivery paths, launch controls, tracking metadata, and retry safety after an uncertain provider outcome.