Fix: Content Generation Activity from GenAI connector does not work in URT [PC-3936] #1309
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
github-actions
bot
added
test:uipath-langchain
dsuresh-ap
force-pushed
the
fix/gen-ai-content-gen-PC-3936
branch
from
464466d to
27d824a
Compare
Pass jsonBodySection from agent config body_structure through to ActivityMetadata so the SDK uses the correct multipart part name.
dsuresh-ap
force-pushed
the
fix/gen-ai-content-gen-PC-3936
branch
from
27d824a to
a96fbf3
Compare
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.
Summary
json_body_sectionfield toActivityMetadatato carry the multipart JSON part name from agent config to HTTP request construction_build_activity_request_specto usejson_body_section(defaulting to"body") instead of hardcoding the multipart part name as"body"bodyStructurespecifies"jsonBodySection": "RagRequest", but the SDK was always placing the JSON body in a part named"body", causing the Integration Service endpoint to return HTTP 400 "The request body is empty"json_body_section🤖 Generated with Claude Code