By default, automations keep debug logs for each executed trigger and action. Debug logs are accessible via the graphical history view:
Automation logs contain information generated by each module within a trigger/action assembly. Generally the information within is useful for trigger/action implementors for troubleshooting.
Automation logs can become voluminous and consume lots of filesystem space, even though they are stored as ZIP files.
Automation logging can be disabled by selecting this menu option:
The menu option will appear like this when automation logging is turned off:
Automation logging can be re-enabled by selecting the menu option again.
Updated 03 Mar 2023
Did this page help you?