Try adding your email as bcc to a run so you can confirm the 50 emails are being generated by the system. Then at least you know the issue is downstream.
if they dont generate then confirm the users are definitely part of the group sometimes user imports can overwrite their group access if they appear multiple times.
Set them up individually and check they go out as individuals you might get a more detailed log record.
In order to be a NPrinting report recipient user needs to have a role in NPrinting. Make sure all people from 50 are at least "Users" or "NewsStand User" or have any other role which allows them to receive reports.
Also do what Andy suggested regarding groups.
On top of that double check whether those users have filters created for them (user filters) which could interfere with your current report.. If they have, make sure those filters are created in seperate NPrinting app on separate connection.
let us know how it goes
Have you resolved this issue，
I have also met this issue recently,
we have 500+ users, but there were 90+ users that could not receive E-mail but others were OK,
All users have the same setup ，Excel file were generated correctly and could sent to local folder successfully，
If you resolved it, could you pls have a share, thanks.
No, I wasn't able to track down the exact cause but users started receiving the report.
I have noticed that if the user does not exist in Qlik Sense app for that day, the report might fail for the user. So check if the users exist in the Qlik Sense app.
As Andy & Lech suggested above check the user groups, roles and user level filters are setup correctly.
I would suggest to upgrade to Nprinting June 2017 version as it has task executions tabs which helps in monitoring. Also, Split the users into multiple groups so you can track down which tasks(groups) fail.
I agree with all other suggestions and I would to add that you could check the SMTP server logs, maybe there could be some error messages related to the email sending process.
Check also the Qlik NPrinting logs in order to find other errors.
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.