Repository navigation
fix(connector): remove invalid CreateDocument response encoding policy - #41
Merged
kundkingan merged 1 commit intoSep 25, 2026
Merged
Conversation
kundkingan
marked this pull request as ready for review
September 23, 2026 07:40
GetEmil
approved these changes
Sep 23, 2026
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
2 participants
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.
Summary
Remove the hand-maintained
CreateDocumentresponse policy that forcesContent-Encoding: deflatewithout compressing the body. It can make Power Automate report failure after GetAccept has already created and sent a document.This keeps GetAccept's custom connector source aligned with the certified connector change in microsoft/PowerPlatformConnectors#4311.
Validation
connector/apiProperties.jsonand verified that deleting this sole policy is the only semantic change.git diff --checkpassed.The certified connector still requires Microsoft's review, certification, and release before customers receive this change.