Hello, I’m running into an issue where the Input and Output Arguments for job execution is null. The job status is Successful and arguments are visible in the Orchestrator Ui. [image] Previously we used the same endpoint on-prem and were able to get the OutputArguments when calling odata/Jobs?%2…

I believe this will explain it :slight_smile: Orchestrator - Rate limits and large data field usage optimization The UiPath Documentation Portal - the home of all our valuable information. Find here everything you need to guide you in your automation journey in the UiPath ecosystem, fro…

Input/Output Arguments not in Orchestrator API Response

Help Orchestrator

Gtzikas (Greg Tzikas) March 17, 2025, 8:04pm 3

Yup, this is the missing link. Thank you for sharing!

1 Like

Topic		Replies	Views
Not getting output argument in response Help	3	1167	September 6, 2019
The output arguments in API response are null Orchestrator orchestrator , api , bug , job	6	3154	December 21, 2022
Get output parameter values through Orchestrator APi services Help	9	2822	December 13, 2023
Start a job does not receive OutputArguments through the Orchestrator API Help orchestrator	2	954	December 13, 2023
How to pass OutputArguments through orchestrator start job api? Orchestrator	2	1439	February 14, 2022

Input/Output Arguments not in Orchestrator API Response

Related topics