Execution log can be found in Setup -> Logs -> Execution log tab and contains all automation execution sessions:

An execution session is created when an automation process is executed, for example, when:

Note. As described in detail in the Context and Sessions article, each form event spawns a new execution sessions, so multiple lines in the Execution log may related to different form events of one user working with the same form.

For each execution session the log shows:

There are standard and detailed levels of logging. When detailed logging is inactive, for each execution session Mapsly only records the list of invoked actions.

When the detailed logging is active, for each sessions Mapsly logs the result of evaluation of every Twig template with a full stack trace of function calls and the content of Context at every step.

Detailed logging can be activated for 3, 6, 12 or 24 hours and then deactivates automatically. Detailed logging can be re-activated at any time, which resets the deactivation timer.

Detailed logging is activated by turning on its switch here:

Click an execution session to see its details. This example content on the screenshot was generated with logging ON:

On the left you see the hierarchical execution flow where Mapsly logged every invoked action, function call and the result of evaluation of every Twig template. You can expand a branch to see activities at lower levels of the execution stack.

If you click any item on the left, on the right you'll see the content of execution context at the moment when your execution item was starting. In the example above, we selected Action execution completed of the last action in the session to see the resulting Context at the time when the execution was finished.