Job processes WebAPI - VisualCron

Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.

Welcome Guest! To enable all features please Login or Register.

westede
Paid support Topic Starter

3 years ago

Hey,

could you please update the job processes WebAPI to give the same result as the dotNET API?
Explained in more detail, the request

https://{vcurl}:{por}t/VisualCron/json/Job/Processes?token={visualLogonToken}&id={jobID}

probably returns only the last job started.
Return Example:

Status               : 0
JobId                : e86a7549-9d19-4dfd-8c8b-d5639330cb84
Id                   : 12
UniqueId             : 983b6624-18b6-4e70-9af1-855e1ac18636
Started              : 2022-06-10T08:15:05.7226003+02:00
ExitCode             : 0
ExecutionTime        : 0,0
PausedTime           : 0,0
ExecutedBy           : uuid:22872778-2dda-435a-9ded-d1182fba0352;id=14
TriggerCPUTime       : 0,0
CPUTime              : 0,0
TasksCPUTime         : 0,0
NotificationsCPUTime : 0,0
OriginalFlow         :
TriggeredFlows       : {}
ExitCodeResult       : 3
WasResumed           : False

In the dotNET API, on the other hand, a complete array of all running jobs is returned.

Best,
Dennis

Sponsor

Forum information

Wanna join the discussion?! Login to your Forum forum account or Register a new forum account

bweston
Paid support

3 years ago

Out of curiosity, What happens if you don't pass it a specific single job ID as your url template implies you're doing? (I don't use the Web API, not sure if what you mean is that omitting the ID raises an error or what.)

Edited by user 3 years ago | Reason: Not specified

westede
Paid support Topic Starter

3 years ago

The endpoint requires an jobid. You can not call the endpoint without an id.

I like to get all of the executing job instances of one job. When the executing jobs is less than x another job starts a new instance of the main job.

bweston
Paid support

3 years ago

Got it. I also have very few jobs that are expected to be running multiple times at once, so it didn't register that was what you meant until after you clarified.