Audit logs for Action Flows
In EMS, you can request a CSV of your Action Flow execution logs, with a link sent to you when the file is ready to download. This download link is valid for seven days, after which you must request a new download.
 |
When downloading your Action Flow execution logs, you can filter by time period, applications, Action Flows, and if the input/output bundles of all single Action executions should be included in the download. You can request a maximum of 2 downloads every 10 minutes.
The file will be in the .zip format, with CSV files for logs in the main folder split so that the size of the files remains easily consumable. The input/output bundles will be included in a separate folder.
Execution logs for Action Flows are recorded in EMS from the moment this feature is released on individual clusters:
au-1 (July 23, 2023)
eu-1 (July 23, 2023)
eu-2 (July 23, 2023)
eu-3 (July 23, 2023)
eu-4 (July 23, 2023)
jp-1 (July 23, 2023)
uk-1 (July 23, 2023)
us-1 (July 23, 2023)
us-2 (April 29, 2023)
us-3 (July 23, 2023)
Other clusters will follow soon.
Logs are stored in EMS for 12 months.
Attribute | Description |
|---|---|
AFlow ID | References the ID of the Action Flow that was executed. |
Execution ID | ID number of a specific execution. |
Execution Type | Available values:
|
Execution Author | Name of the user who started the automation by using the Run Once button (in this case, the Execution Type would be Manual or Instant, depending on the first module), or by using a connected Action Button (in this case, the Execution Type would be Scheduled). |
Module ID | ID of the module used in the execution. |
Operation | Operation index |
Cycle | Cycle index |
App | App name and its label (where applicable) |
Module | Module name and its label (where applicable) |
App Version | Version of the app used in the exection. |
Start Timestamp | Provided in the UTC standard. |
End Timestamp | Provided in the UTC standard. |
Status | Available values:
|
Error | The error message with which the execution failed. |
Connection |
|
Target System | The server targeted by the execution module. |
Target API | The target API. For example, for SAP this would be the RFM name such as BAPI_SALESORDER_CHANGE |
Agent ID | The agent ID in EMS |
System Connection | Contains the system connection configuration identifiers provided in the cloud, value is {id} ({name}) |
IO Bundle file names | Location of files of the Input/Output bundles for that execution. |
The IO CSV file contains the following attributes:
Important
The downloaded data is identical with the data visible in the Action Flow history. This also means that if the Data is confidential setting of an Action Flow is activated, no input/output bundles will be available.
Attribute | Description |
|---|---|
Execution ID | ID number of a specific execution. |
Module ID | ID of the module used in the execution. |
Operation | Operation index |
Cycle | Cycle index |
Page | The page the output belongs to. |
Total Pages | The total number of pages that the output bundles had when there are multiple bundles for a single module, for example, Get Rows. |
Error | Boolean flag showing whether the bundle belonged to a failed execution. |
Input | Boolean flag showing whether it is an input or an output bundle. |
Value | Content of the bundle |