--- title: "Using the Log Step" slug: "using-the-log-step" description: "This document shows users how to use the Log step within a flow to create Logs in Decisions. This provides users a record of any issues encountered within the platform. The Log Step offers users customization regarding the category, type of level, and message attached to the logs that are created by the step. " tags: ["Event logs", "Error Handling", "Logging", "Logs", "Using the Log Step"] updated: 2025-06-24T16:24:48Z published: 2025-06-24T16:24:48Z --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt > Use this file to discover all available pages before exploring further. # Using the Log Step ## Overview [**Logs**](https://documentation.decisions.com/v9/docs/logging-overview) provide a record trail for any issues encountered within the environment. It is a best practice to include logging within a process in case any users/end-users are to occur an error during runtime. The **Log**step is main step used to create logs when a Flow reaches a particular outcome path. The following example demonstrates how to use and configure the Log step within a Flow. --- ## Configuration The Log step comprises of three main settings: **Type**, **Category**, and **Value** input aka the log's Message. ### Types Also known as **Levels**, this setting declares the level of importance and severity of the error described in the log. The following default types are as follows: | Type Name | Description | | --- | --- | | **Info** | This provides information to the user on an occurrence and is typically used outside of error tracking. | | **Debug** | This catches most exceptions that do not fall under the other categories. | | **Warn** | This tracks potential issues that do not impede the process from running. These are typically less critical issues. | | **Error** | This tracks when a process cannot complete properly. | | **Fatal** | This is an environment breaking level warning that stops a process (or multiple processes) from running. | **Fatal**and**Error** types are also logged as Windows events for monitoring by external tools. ### Category This setting prompts for the log category that the log and its error may fall under. It recommended to make a log's category as easily identifiable as possible. For example, [default System log categories](https://documentation.decisions.com/v9/docs/reading-logs#:~:text=the%20occurrence%20triggered.%C2%A0-,Server%20Log%20Categories,-The%20following%20list) denote errors in specific logic within Decisions such as Forms, Rule Engine, ORM, etc. Users may enter one of these pre-defined categories or create their own [custom log categories](/v9/docs/creating-custom-log-files). This is recommended for extensive processes name the Log step's category after the Flow producing the error such as "Payment Verification Flow". ### Message This setting prompts for the message the log provides once generated. The more descriptive message the better for any future troubleshooting. As with any other text input, information here may be set statically, dynamically, or with merge plain/HTML texts according to their appropriate [mapping types](/v9/docs/input-output-types-overview). --- ## Example 1. From a **Designer****Project** click the **CREATE****FLOW**button on the **Global****Action****Bar**, then CREATE a new **Flow**. 2. From the **Flow****Designer**, attach a **Log**step from the **Toolbox > FLOW MANAGEMENT >****ERROR****HANDLING**, to the **Done**path of the **Start**step and the **End**step. 3. From the **Properties**of the **Log**step, under **SETUP LOG > Type**, select the desired level (in this case **Fatal**).  ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-24_12h12_28.png) 4. Under **Properties > Category** on the **Log**step, provide an easy identifier (such as the name of the **Flow**/Project/etc...)  ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-01-06_12h27_50.png) 5. Under INPUTS, select **SHOW****EDITOR**. Then, configure the message in the Merge Text Editor by inputting "Logged from Flow-". Afterward, expand the **Flow****Data**tree on the right and **Add**the **Flow****TrackingId**. Then, click SAVE. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-24_12h20_02.png) 6. **Save**the Flow, then close with **X**. 7. From the **Designer****Studio**, right-click the **Flow**and select **Run****Flow**. 8. After the **Flow**runs, navigate to **System > Administration > System Tools > Logging**and view the Log of the Flow. Log Local File System LocationThis **Log**can also be viewed from the **Decisions.Web.Core.txt** file located in the **Logs**folder on the **Local****File****System**. If the default installation location was used for the environment, then this file can be located at **C:\Program Files\Decisions\Decisions Server\Logs**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-08-20_12h38_20.png) --- For further information on Flows, visit the [Decisions Forum](https://community.decisions.com/categories/Flows).