Journey task expiration: the task should not arrive to the recipient

Summary:

Content (please ensure you mask any confidential information):

Hello everyone,

we would like to ask a question about the system behavior regarding the expiration of a task of a journey. We noticed that if a task is not completed and expires, the next task still arrives at the recipient. Is this the expected behavior? It would not be logical because if the first task was not completed, the next one should not even arrive at the recipient.

Thanks,

Silvia

Version (include the version you are using, if applicable):

Code Snippet (add any code snippets that support your topic, if applicable):