Hi, naveenanda_vam 

Thank you very much for the very useful information. I guess the cause of the problem lies on the visual querying data source. In the official Power BI documentation, it is mentioned:

Set visual query limits in Power BI Desktop - Power BI | Microsoft Learn

When you try to subscribe for more than one person, the memory is exceeded. As far as we know, the content of a Power BI capacity isn't unlimited. Each license has a memory limit. A single person can't outdo it, and multiple people will send query requests to the data source in real time, which will consume exponential increments, causing us to quickly reach our limit.

Here's what we can do:
1. Try scheduling your subscription for a time period when no one is watching the report. Watching reports also requires memory that consumes your capacity for a live connection.
2. Try to reduce the number of people you subscribe to at a time, and don't add all of them to your subscription at once.
3. I think this one is the most user-friendly, try to group different groups of people, and then the important people will arrange the subscriptions individually. People who need to see the same content will only subscribe once and then forward an email to the group (or subscribe directly to the group).
The above method will be a good way to circumvent this limitation. If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.

Best Regards

Jianpeng Li

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi naveenanda_vam 

The EmailSubscriptionScreenshotVisualError happens when Power BI cannot connect to the data source while fetching data for a report. Possible causes include:

1. Data Source Connection: Check if the dataset is connected properly, and ensure authentication is correct.
2. Service Limits: Multiple simultaneous report schedules could overload the service. Consider spacing out schedules to avoid bottlenecks.
3. Licensing: Premium Per User (PPU) should allow better performance, but still check for concurrency issues.

Solutions:

• Re-authenticate the data source.
• Check Power BI Service Status for disruptions.
• Try scheduling reports at different times.

Did I answer your question? Mark my post as a solution, this will help others!

If my response(s) assisted you in any way, don't forget to drop me a "Kudos" 🙂

Kind Regards,
Poojara
Data Analyst | MSBI Developer | Power BI Consultant
Consider Subscribing my YouTube for Beginners/Advance Concepts: https://youtube.com/@biconcepts?si=04iw9SYI2HN80HKS