Issue with scheduling of an email report

We are having an issue with the dashboard scheduled email function. We typically provide access to dashboards via shared folders and do not specify users or groups on the individual dashboard, previously, scheduling an email worked with this structure.

However, with the recent change to the schedule functionality, subscribers do not been receive an email when they subscribe to the dashboard, when they have checked the subscribe button. We have tested a few different sharing scenarios to try and get the email to the subscriber:

via shared folder permission via group - schedule button visible and subscribed, the subscription is visible (green with a tick) in the Edit Schedule panel (dashboard owner as initial recipient) - no email

via group directly in dashboard - schedule button visible and subscribed, the subscription is visible (green with a tick) in the Edit Schedule panel (dashboard owner as initial recipient) - no email

via group directly in dashboard - schedule button visible and subscribed, in the Edit Schedule panel (group as initial recipient) - everyone in group gets email

via named user directly in dashboard - schedule button visible and subscribed, the subscription is visible (green with a tick) in the Edit Schedule panel (dashboard owner as initial recipient) - gets email

In summary, it seems that sharing a dashboard via a group (either by folder or directly) will present the subscription option and if selected will show a subscription in the edit schedule panel but will not send the email, However, the same users can receive and email as a named user on the dashboard or if the group they are in is added in the email recipient in the schedule edit panel. Is this being experienced by anyone else???

hi @tonyjs

Thank you for letting us know. I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!