Each project has its own log file that is automatically created if it doesn't exist when the project is created or opened. The Log File is a database which stores detailed information of previous builds and also a summary record of all past builds for the particular project. It is important to decide how many detailed logs you want to store in the log file, as this makes a significant difference to the size of the log file on disk if you have a large project. There are three pages of logging options.
By default, Static logging is used. This means that when a project is run, all events are written to the project's log file, but they are only displayed on the Build Log tab when the project stops.
Alternatively, Live logging means that as each event occurs, the Build Log tab is updated. This is useful for debugging, but is much slower, especially when running large numbers of quick actions.
These options filter the amount of information displayed in the log. All information that the action generates is always stored in the log. Each action is responsible for tagging a status message with either Success, Information, Warning or Error. It's possible that some actions may not correctly tag the message, especially actions that rely on a 3rd party executables as it can be difficult to detect if certain command line output are errors or informational for example.
Show Hidden Actions: Displays "hidden" actions in the log if they execute in error. See Action logging properties for information on hidden actions.
These options control how logs are exported from the Export Log Action.