Unexpected error occurred using export table in executions
search cancel

Unexpected error occurred using export table in executions

book

Article ID: 385313

calendar_today

Updated On: 01-06-2025

Products

Automic SaaS CA Automic Workload Automation - Automation Engine CA Automic One Automation

Issue/Introduction

When attempting to use the "Export table" button on an object in the AWI, choosing Monitor -> Executions

the following error occurs: An unexpected error occurred. Further details are available in the logfiles.

No error shows in the AWI log file.  Turning on tracing for the AWI in client 0 shows the following in the log:

2025-01-06 20:43:22,283 -jsse-nio-8443-exec-15 [TRACE] my AUTOMIC:100/AUTOMIC/AUTOMIC 97BDC87C6A0EAFA0A5227D2A88C77B1F-1 0000000001482015  [com.uc4.ecc.framework.entrypoint.ui.MainEntrypointView] - Sudo into UI MainUI 97BDC87C6A0EAFA0A5227D2A88C77B1F-1 
java.lang.Throwable: null
    at com.uc4.ecc.framework.entrypoint.ui.MainEntrypointView.sudo(MainEntrypointView.java:486)
    at com.uc4.ecc.framework.entrypoint.ui.MainUIErrorHandler.handleError(MainUIErrorHandler.java:53)
...

Environment

AWI version 24.2.0

Resolution

This is a known issue that no longer occurs in 24.3.0.

There are two possible workarounds while still below 24.3.0

Workaround 1 (done through Process Monitoring)

  1. Right-click on the object and choose "Monitoring" -> "Show in Process Monitoring"
  2. On the right side click the "Filter" button
  3. Be sure the filter is done by task name
  4. On the bottom of the filters, choose "Include deactivated tasks"
  5. For timeframe, put in the time frame you'd like to use - I'd recommend using "All tasks in timeframe" and a day of time or the default of 12 hours, but longer can be used if necessary
    Click the "Filter" button
  6. Use the "Export table" button in the upper right of the Process Monitoring screen


Workaround 2 (using REST API)

Use the REST API executions endpoint, documented here.  Here is an example of what could be used:

https://{REST API Endpoint URL}/ae/api/v1/0100/executions?name=JOBP.WORKFLOW_NAME&include_deactivated=true&time_frame_from=2025-01-01T00:00:00Z

Please note the following parameters:

name - the name for the object.  In my example above, this is an object called JOBP.WORKFLOW_NAME
include_deactivated - in order to not just show active tasks, this must be set to true
time_frame_from - this is the lower bound of the timeframe to show and is mandatory when using include_deactivated (or else will just show the last 12 hours).  Format is YYYY-MM-DDTHH:MM:SSZ

Powered by Wolken Software