Steps to reproduce

• In the general settings -> email, configure a configure an email batch size of 5
• Create any survey and start it, making sure it uses participants
• Add 5 participants with an email address, with a validity that starts in the future
• Add 5 more participants with an email address that are valid now
• Use RemoteControl API invite_participants to send invitations, without specifying specific participants to invite (so aTokenIds = null).

Expected result

There are 5 invitations sent, for the 5 participants that are valid now. The first 5 participants should be completely disregarded.

The same problem happens if the first 5 participants do not start in the future, but end in the past.

It does work as expected when a valid participant does not have an email address at all. In that case, the participants that cannot be invited are ignored.

Actual result

No invitations are sent. I feel like it's querying the first 5 of all the participants that have not received an invitation yet, and going through those, and then deciding not to send anything because none of them are valid yet. Participants that are not valid yet/anymore should be disregarded for this process completely, not queried first and then filtered out.

It should apply the same logic as it does for participants without an emailaddress for participants that are not valid yet/not valid anymore.

The effect of the current behavior is that large surveys with many participants that become valid in the future, may not send any invitations at all, even if there are participants that can be invited.