Flood control for actions

That's an interesting requirement, and from my POV this is something that needs to be solved with logic that is not ECA related - it requires a solution that would be applied in each context/toolset that would be used to implement this.

What's required is some stateful system. The workflow would have to define a ruleset, e.g. like described in the above issue, where the state is being saved per user, and notifications will then be sent by another model which reads the state and then takes some action following the previously defined rules.

As for ECA, it is possible to write and read state values. Or you can add a field to the user entity, that is otherwise invisible (from the form and the profile view) and keeps the state information which helps you to decide, whether a notification should be sent or not.

Hi Jurgen,
I know it's not an ECA related problem.
Since I use ECA for notifications in the above scenario, I wanted to get advice by thinking if I can solve it with ECA again.

I will listen to your advice. By the way, I would be very happy if you could evaluate this scenario at tube.tchncs/ecaguide

Thanks

Since I use ECA for notifications in the above scenario, I wanted to get advice by thinking if I can solve it with ECA again.

Sure, like I commented before, you need to store the state information somewhere, either in Drupal's state system or with the user entity. And then you can make your decision inside ECA based on the stored state information and your specific conditions. Not sure what else I could advise. Going deeper would have to go into data modelling and so on, which is a bit too much to ask for as free support.