Record Event Log Step

The Record Event Log step is used to log record information for a processed run.

Praise Magidi avatar
Written by Praise Magidi
Updated over a week ago

All Synatic flows contain a Log Record Error step at the end of each flow by default. This step is used for logging the records that are processed during a flow run. A tally is kept of records that are completed successfully, records that are in error, and records that were excluded or skipped due to filtering. This assists in debugging. Other dataset line items that represent headers and footers are also logged.

Illustrated in the image below is an example of a flow that has a Record Generator as a source step. The record information is logged in the Record Event Log step.

Adding a Record Event Log Step

To add a Record Event Log step in a flow, follow the below instructions:

1. Click on the highlighted icon as shown in the below image.

2. The below page will appear. Click on the RecordEvent tab and select Buffer as shown in the image below.

Configuring a Record Event Log Step

Illustrated in the below image is the configuration that is available in the Record Event Log step.

Events – The events to trigger on. This field is required for the step to work. The following options are available:

  • Completed – Log all records that are successfully processed.

  • Error – Log all records that contain errors.

  • Skipped – Log all filtered and excluded records.

  • Header – Log all line items that are identified as a header within the dataset.

  • Footer – Log all line items that are identified as a footer within the dataset.

Max – Set the maximum number of records to log. If more than one event is selected, please note that it will show the status of the records that were processed first.

Clean Record Checkbox – Remove the record details from the log and retain only record headers.

Save Parameters Checkbox – Save any parameters associated with the flow in the log.

Batch Size – Set the number of records to cache before submitting to the log.

Troubleshooting/Debugging a Run

For more information on how to troubleshoot/debug a Run, please click the link below:

Did this answer your question?