Automic Workload Automation

 View Only

  • 1.  Issue with Retrieving Failed Executions (Status 1800-1900) via API

    Posted Apr 25, 2025 01:01 PM

    I'm experiencing inconsistent behavior when trying to retrieve failed executions with status codes between 1800-1900 through the API.

    What I've Discovered

    When I manually trigger an error and check the run ID, I can see the failure details:

    json
    {
      "name": "APP.DB.LIST.UPDATE",
      "type": "JOBS",
      "queue": "CLIENT_QUEUE",
      "run_id": 121710216,
      "status": 1800,
      "status_text": "ENDED_NOT_OK - aborted",
      "runtime": 0,
      "activation_time": "2025-04-25T15:25:55Z",
      "start_time": "2025-04-25T15:25:56Z",
      "end_time": "2025-04-25T15:25:56Z",
      "agent": "SQL_MSSQL",
      "platform": "SQL",
      "parent": 0,
      "reference_run_id": 0,
      "user": "USER",
      "estimated_runtime": 1,
      "alias": "APP.DB.LIST.UPDATE",
      "activator": 120871956,
      "activator_object_type": "USER"
    }

    However, when I attempt to query for this same execution using:

    ...v1/1010/executions?status=1800&time_frame_from=2025-04-25T15:25:55Z

    I get an empty result:

    json
    {
      "total": 0,
      "data": [],
      "hasmore": false
    }

    When running without parameters, I receive 827 executions, which seems accurate.

    Potential Issues

    1. Could there be a misconfiguration in some setting that's affecting the status filter?
    2. I've also noticed the API doesn't seem to return executions that don't have a "Start Time" - for example, if the execution failed before even starting.

    Has anyone encountered similar behavior or can suggest what might be wrong with my approach?



  • 2.  RE: Issue with Retrieving Failed Executions (Status 1800-1900) via API

    Posted Apr 25, 2025 01:05 PM

    I've considered brute-forcing all possible run IDs, but this would be a last resort approach. However, missing any failed execution is not acceptable, I need 100% reliability in identifying failures. I use Automic 21.0.5.




  • 3.  RE: Issue with Retrieving Failed Executions (Status 1800-1900) via API

    Posted Apr 29, 2025 12:03 PM

    When doing /ae/api/v1/0015/executions/{runid} this will return the results you showed in the first json box. Using this doesn't care if its deactivated or not.

    When searching with GET /executions it does not include deactivated tasks by default, this likely the cause for no results.

    Try with "v1/1010/executions?status=1800&include_deactivated=true&time_frame_from=2025-04-25T15:25:55Z" that should get you the expected results.