Automic Workload Automation

 View Only

 Objects Executions via REST API

Matthias Schelp's profile image
Matthias Schelp posted Jul 23, 2025 06:39 AM

Hi Folks,

Short question. Is there a way to get the executions of an object via REST API. I know I could get it with an SQL or the Java API, but I am limited to REST Calls only.

The only thing I found was the 

/{client_id}/executions

endpoint. But this doesn't seem to do the trick.

Regards,

Matthias

Oana Botez's profile image
Broadcom Employee Oana Botez

Hi Matthias,

The executions endpoint has multiple filters that can be set to get executions for a specific object https://docs.automic.com/documentation/webhelp/english/all/components/DOCU/24.4/REST%20API/Automation.Engine/index.html?overrideUrls=../Automation.Engine/swagger.json,../Analytics/swagger.json,../Infrastructure.Manager/swagger.json#/execution/listExecutions

If the executions have already been deactivated, you need to specify this in the REST call and also the timeframe to be considered, for example:

GET https://<url>/ae/api/v1/100/executions?name=JOBS.PYTHON.UNIX.TEST&include_deactivated=true&time_frame_from=2025-04-15T06:37:59Z


BR,
Oana

Peter Grundler's profile image
Broadcom Knight Peter Grundler

Hi Matthias,

if you have tried it with the REST call it would be interesting to check the results.

What I experienced is

  • the call including deactivated entries works in v21 (21.0.14) and provides valid results
  • the same call in v24 (even 24.4.1 HF1) returns information from process monitoring but no historic data.

To me is looks like the parameter "include_deactivated" is not recognized/used. I can reproduce it on my system and a customer environment.

I have asked @Oana Botez to very this.

regards,
Peter

Matthias Schelp's profile image
Matthias Schelp

Hi Peter,

for me it is the other way round. It didn't work in 21. Or better said it was veeeeery slow. But since we updated to 24 it works. Looks like we've had some kind of DB performance issue. 

But: In both versions it doesn't do what I would expect. Example. If I have a job that runs every minute, I can see 999+ executions in the webinterface. The REST call, with "name" and "include_deactivated" set to true only gives me 143. Looks liek there is some kind of default timespan that is not documented.

If I set "time_frame_from" to a date 2 years ago I get I get all executions.

Regards, Matthias