docs(teams): investigate repeated image timeouts and plan hardening - #63
Merged
Merged
Conversation
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.
The latest Teams image failures still reach the 30-second body-transfer deadline. PR #61 contains the 60-second correction, but remains unmerged.
This draft records the evidence and a Teams-only repair plan. It changes one document under
docs/teams/and contains no runtime change.The plan requires a deployment retest of PR #61 first. If failures remain, it defines request-local transfer diagnostics and repeat-transfer tests across Teams actor routes. It preserves the existing attachment policy, terminal acknowledgement, cancellation, and safe-text behavior.
Evidence: one verified 376,953-byte PNG succeeds; two personal downloads fail near 30 seconds with
stage=bodyand no outer cancellation. The channel-thread screenshot shows the same visible symptom, but its transfer stage remains unverified.Validation: local document links, UTF-8, BOM checks, and
git diff --check. Runtime tests are not applicable to this documentation-only change.Related: #61 and #62. The owner reviews, monitors CI, merges, deploys, and retests. This PR does not establish live transfer reliability.