Monitor Custom Filter consumed all our Action quota

Hi, I wanted to know if it's expected that running a custom filter on a Monitor consumes the Action quota.

:computer: Environment
We enabled a Monitor custom filter yesterday and today we realized we had ran out of Action quota.

The Monitor was supposed to trigger an Action when the custom filter passed. Although the Action didn't run a single time, we ran out of quota.

:1234: Code to reproduce
The custom filter is making use of the KeyValueStoreClient and ethers dependencies.

Hi! this is not expected behaviour, we will work on get this fixed ASAP

Thanks for reporting