**Self-Hosted Org**
How do you you guys troubleshoot when scheduled reports fail to send? Particularly when it is not ALL the scheduled reports that failed but random failures her and there. Every couple months here a couple reports will fail to send. It is not all of them and it is not always the same ones that fail. I checked the queue and the schedules - nothing there is off except for the fact that it didn't run. I usually submit a help desk ticket when this occurs, but I am interested in know what other clients are doing to troubleshoot this because I never really get anywhere with my help desk tickets regarding this subject.
Ashley Elliott
Database Administrator
St. Louis Symphony Orchestra
314-286-4198
ashleye@slso.org
Ashley,
(RAMP) Not saying this is your issue, but we used to have a lot more scheduled reports failing. This usually happened because we had the same exact report scheduled multiple times to start at the time exact time. Like, there is a report we use for 75% of our scheduled reports because it is the one we use for performance revenue reporting. Given that, it was scheduled often, sometimes 2 and 3 slightly different parameter variants all starting at the same time. And sometimes one of those would fail to send.
We simply started spreading them out. We adopted a policy that, excepting very specific reports and circumstances (and we usually deferred here to the Finance department), we would NOT schedule any reports at the exact same time. So we adopted a sort of "every three minute" policy. So, 6:30 AM for one, then 6:33, 6:36, 6:39, etc... for all morning scheduled reports. I wrote a local view which is visible in the System Tables so any staff members who schedules reports can see for what dates and times reports are scheduled, so those times can be avoided. Since we went to that method, we have had an extremely low count of failed reports, and usually those were caused by something completely different to which it could be attributed.
Just in case that might be an issue for you, thought I would pass that on. Either way, best of luck!
John
That is great information. In today's case of failed schedules, they are the same report but scheduled at different times. But I can see that being the issue for a case that happened a few months back.
Would you be willing to pass along the script you used to create that local view?
Ashley
Happy to pass it along! Now, this is a local view, and I already have a customization in place which allows our users to see local views in System Tables. Not sure how much that will impact the use of this view for you, but just wanted to mention it.
Hi Ashley, is there a specific error you can share? We've been dealing with failing reports (they run, but don't email), due to a bug in the latest SP of v15.1.
Unfortunately, I don't have an error to share. My coworkers will submit a (internal) helpdesk ticket when they don't receive the emailed report they were expecting to receive. Then I go about trying to figure out why they didn't get the email.
So like I said, there is no specific error, but they I have this screenshot from failures on this past Thursday and Friday. Looks like they just didn't run. Any thoughts?
**SOLVED??**
In this specific case, there was a user who scheduled a bunch of reports that no longer works here (my predecessor). We removed that user from some user groups (since they don't work here anymore), but didn't reassign the owner of the reports. Tessitura was trying to resolve these reports and it was causing a bottleneck with other reports.
So... yeah, make sure you check report schedules if you have to make adjustment to a user or user groups.