We've been working on integrating with the Reporting features on the Tessitura API for one of our clients lately, and we've recently ran into some issues. When I first started working on this (around 5/12/21), we were able to generate Report Schedules and direct Report Request calls that would successfully execute on the Test server (it never worked on the Prod server). Around 5/28/21, the reports requests stopped executing on the Test server as well, and are now stalled in queue with a QueueStatus of "s". We've been trying to debug this without much success, so we have a few questions to try and debug it.
What User, User Group, Resource, and Security permissions are required to generate a functioning Report Schedule as well as do direct Report Requests calls? We want to ensure that our users are configured correctly. Currently, we're attempting to generate them using both an Admin and Non-Admin account.
David Dwiggins,
It's good to know that I'm not alone. We were compelled to move to AWS mid-June 2021. We have had a support ticket open for about a week now.
I'm wondering if anyone else out there is having the same problems.
I'm also wondering what might be similar between your organization and mine.
Hi Tom and David,
Boann here with the Support Escalation Team. I have reviewed your open support tickets on this issue and based on what we are seeing in our troubleshooting thus far, it does not seem like the issues are related. We are continuing to investigate both issues, and understand how frustrating it can be to have a report run slowly or not complete. We will continue to keep you updated on our progress within each support ticket.
Thank you,
Boann Petersen
Support Escalation Manager