The first condition in the filter fails:
If you don’t know what the filter does, remove it. Maybe you added it in earlier versions of the scenario.
It appears to be checking the age of the event, which is probably already checked in the first module, as far as I can tell from earlier comments
Thanks for the fast response @Loopz I know the guy who set this up, put there that filter because we were running into problems every time the scenario would check for submissions and there were none.
Then we would have errors all the time, I guess because it was sending empty data? I am not sure
What I did to check if the scenario is working is to change the filter to addDays also to match the settings of the first module, and it worked properly, so I set it all up as it was before, but with the 60 min.
Do you think if on the second filter, I only use the condition that the email must be not empty, will work also?
Yes, having the same filter a second time doesn’t make much sense from what I can tell (based on what I read so far)
Totally understand what you mean, I am a bit hesitant to change it just in case seems it seems to be working now.
The logic behind this was as follows:
Module one checks every hour for new form submissions. And these submissions are then sent to module 2.
The first filter checks that the submissions are new or submitted within the previous hour (seems redundant to me, you are right) and it also checks that the email is not empty (this basically makes sure in case there are no new submissions, there is no data pushed through)
I may try to remove that second filter and see what happens 
