Currently, if we set up an Workflows with a condition like If Status is [Label], and we later deactivate that specific status label in the column settings, the entire automation fails and throws an execution error.
Deactivating a label is a standard way to clean up boards without losing historical data. However, the fact that it breaks existing automations forces us to keep obsolete labels active (which defeats the purpose of the deactivate feature) or use complex workarounds.
Proposed Solution: The Workflows engine should not fail when it encounters a deactivated label in a condition. It should simply evaluate the condition as false (since no new items can be assigned this label anyway) or gracefully ignore it, rather than triggering an execution error that disables the automation.