Repository navigation
feat(tasks): [1/2] accept task_source_metadata in create_quickform_async [ACTN-11909] - #1948
Draft
Sahil-Wakode wants to merge 4 commits into
Draft
Sahil-Wakode wants to merge 4 commits into
Sahil-Wakode wants to merge 4 commits into
Conversation
🚨 Heads up:
|
Sahil-Wakode
force-pushed
the
feat/quickform-task-source-metadata
branch
from
October 22, 2026 09:41
6b8b66c to
ff73d76
Compare
|
This branch has not been deployed
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
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 this PR does
Lets
create_quickform_asynctaketask_source_metadata, the same waycreate_asyncalready does.task_source_metadatais a dict of extra keys. They are added to the task'staskSource.taskSourceMetadata, next to the keys the SDK already sets (InstanceId,FolderKey,JobKey,ProcessKey).Why
Action Center now writes task events (created, assigned, completed) to the trace. To show them under the right step, it needs to know which span the task belongs to. The code that creates the task sends that as
ParentSpanIdintask_source_metadata.Agent escalations create two kinds of tasks: app tasks (
create_async) and quick form tasks (create_quickform_async). App tasks could already send it; quick form tasks couldn't. This fixes that. The escalation tool change that sends the span id is in uipath-langchain-python (part 2).Changes
_tasks_service.py:create_quickform_asyncand_create_quickform_spectaketask_source_metadataand pass it to_apply_task_source. The synccreate_quickformis unchanged.test_actions_service.py: a test that the extra key is sent andInstanceIdis still there.uipath-platformversion bumped to 0.2.42.Testing
test_actions_service.pypass. The new test fails without this change.ruff formatandruff checkpass.