Is anyone familiar with this error? It's a scheduled emailing that executes on Monday at 5pm EST. It's not a consistent error, once every few weeks or so. Ticket with Tess hasn't resulted in any answers. The dashboard has been rebuilt from scratch with no resolution of issue and there's another dashboard, built using the same table and structure but is broken down by restriction rather than donor category which has never had this issue.
Hi everyone,This particular error can be caused by a number of things, some examples would be:- The timing of the send, maybe it clashes with the data load or routine maintenance (meaning the elasticube may be unavailable) it could be that the server has a high volume of large dashboards / recipients scheduled at the same time that we need to look into.- It could be email timeout settings if the dashboard is big or has a lot of pivots, and takes some time to generate, which I think is what Christine referenced in her reply.- Something in the dashboard, such as a single widget, may be having difficulty generating the results to provide for the email.- Or it may be the recipients, maybe a recipient doesn't have access to the data source for a widget in the dashboard.Generally you can identify whether it is something server, timing, or volume related by testing if this sends using the "send me a report now" function on the share/republish screen at a different time of day. If the report sends, then that would indicate that there isn't a problem with the dashboard itself if it sends successfully to just yourself, and therefore another factor is likely at play.If the "send me a report now" function takes some time, and produces an error, that would indicate that something in the dashboard is having problems. In those instances, one troubleshooting method would be to duplicate the dashboard and remove one widget from the dashboard at a time and test the send after each widget removal until the dashboard successfully sends. And then go back to the original and test just removing the last widget you removed from the duplicate to see if you can isolate it to a widget and then work from there to try to find what might be causing that widget to error when sending.As always, we are happy to help look at these via support tickets as they will all likely be different resolutions and specific troubleshooting around each dashboard will help to get to the bottom of the problem and get them sending consistently without these errors.
William Ingramm I have found your ticket that you had initially where this looked to be fixed, but it sounds like you are still having issues, so I have re-opened that and will be in touch to look at this one for you.
Thanks,James DavisSupport Escalation Specialist
James Davis said: Or it may be the recipients, maybe a recipient doesn't have access to the data source for a widget in the dashboard.
I guess that makes sense, but I would have never thought about that.