Automation Editor
...
Gear Menu
Processing menu
Disabling logging
2min
By default, automations keep debug logs for each executed trigger and action. Debug logs are accessible via the graphical history view:
![Document image Document image](https://images.archbee.com/Y2QGD8otsIOv4e0hQQnqa/kjAGQpCSaKtTCztG_ciIB_image.png?format=webp)
![Document image Document image](https://images.archbee.com/Y2QGD8otsIOv4e0hQQnqa/S8GCIQnmk56zQQgYFALNM_image.png?format=webp)
![Document image Document image](https://images.archbee.com/Y2QGD8otsIOv4e0hQQnqa/74_6Xc1Pg-ZFpD7ShkSyM_image.png?format=webp)
![Document image Document image](https://images.archbee.com/Y2QGD8otsIOv4e0hQQnqa/zdnPbXZWBLHqeT3LAQRcV_image.png?format=webp)
![Document image Document image](https://images.archbee.com/Y2QGD8otsIOv4e0hQQnqa/fdzTooUrjlV_GuBRK5IYi_image.png?format=webp)
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:
![Document image Document image](https://images.archbee.com/Y2QGD8otsIOv4e0hQQnqa/UCxbN42jtI-al6-9LhJNr_image.png?format=webp)
The menu option will appear like this when automation logging is turned off:
![Document image Document image](https://images.archbee.com/Y2QGD8otsIOv4e0hQQnqa/iJvzmcaSLmHjR0cb7P9BF_image.png?format=webp)
Automation logging can be re-enabled by selecting the menu option again.
Updated 28 Nov 2023
Did this page help you?