Process execution log files

It is simple to capture data about process execution. Log files can quickly become very large. Typically, log files are disabled for normal processing on production systems.

The paragraphs that follow explain what kind of data is captured in the various log file settings and how to enable logging.

Logging settings are available from the Process Definition dialog box which is available when you create or edit a process definition. You can also specify logging settings when you upload a process using Infor Process Designer.

Available work unit logging levels are:

Disabled: No data is stored in the log file. Consider using this setting for a process that is running successfully and is not in need of troubleshooting.
Enabled: The log file captures data about work units only as they are created and move through the system.

Any selection in addition to None can negatively affect performance.

Note: Each activity node within a work unit can retain a maximum of 1 MB of log data per run. For example, if an Assign activity node runs within a loop 100 times, it can generate up to 1 MB of logs per iteration. This results in a total of 100 MB. If the log output from any activity node exceeds 1 MB during a single run, the system trims the output to retain only the most recent 1 MB. This ensures visibility of newly added log entries.

This limitation applies only to work units in non-production tenants. Production work units continue to log without this limitation until further notice. This limitation affects only the logging behavior. Activity notes can still generate output that exceeds 1 MB. This output remains fully accessible within the flow. The 1 MB limitation applies only to the amount of log data retained per run. It does not affect the actual output that the activity node produces.