Bizagi, just as any other application, generates errors or warnings that you can access through the Event log. These messages are generated in multiple situations: for example, when case execution comes to a point where an activity action involving an incorrect XPath is executed; or when the system flushes temporary files.
The Event log option lets you consult event files generated during the execution of a project deployed on Automation Service.
In this image, four features are highlighted:
1. Filters: Using the Date from and Date to inputs, as well as the Levels list, you can limit the list of the messages displayed to more easily find the file you want.
2. Event logs: Each row of the table is a different event. Click 
to expand the event so you can review the whole event message.
3. Select logs: Select a set of messages to delete them. When you select at least one message, the delete option is enabled.
4. Export csv: When you click this option, the system prompts you to provide a file name and location on your machine to save the event logs. This action generates a CSV (Comma Separated Values) file containing all event logs, and their associated details for you to review or store.
Bear in mind that the visualization limit for the event logs file is 10.000 records, and that these records are displayed in blocks of 1.000 records (rounding up). This means that if the event logs file has 2.500 records, the file you download will contain 3.000 records.
|
If you need to increase the event logs file visualization limit, contact the Support team through a ticket. |
Last Updated 6/15/2023 5:25:15 PM