Assignment creation notifications don't work

If you are on a on-premise vault, you can check windows event log for failures of delivery. Probably it's because of default settings of M-Files. When a user forwards an object in a workflow to another user, 

M-files tries to set previous user as sender while logging to the e-mail server as the user set in notification settings. This is called impersonation and it's not allowed by e-mail servers by default. You can turn it off from Advanced Vault settings

Hi, Cagrie,

Thank you for your help.

I am using a vault in Cloud M-Files.

This behavior is strange because users receive email notifications when the assignment is completed but not when the assignment is created.

Could there be a block on server emails?

Hi, Cagrie,

Thank you for your help.

I am using a vault in Cloud M-Files.

This behavior is strange because users receive email notifications when the assignment is completed but not when the assignment is created.

Could there be a block on server emails?

Are you perhaps modifying the permissions of the object in the same workflow state where the assignment is created? This can cause issues like you are describing since the user needs to have the rights to see the object for the notification to be sent and there's a timing problem if you try to give these rights simultaneously with the assignment creation.

If that's the case, try modifying your workflow so that you first give the permission to see the object in one state and then create the assignment in the next, separate state to which you can move with an automatic state transition.