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.
Hi everyone,
We finally resolved the issue with the help of Tessitura, and I wanted to share what we found.
The issue happened when create a Report Request / Report Schedule using a user that was either inactive or not assigned to a valid user group. Once created, whenever the queue processor runs, it halts once it hits the report request with the invalid user (or user w/o a user group). Any request after that would not run either. This can affect more than just the user that created the report request. To fix, simply remove the report request(s) or schedule(s) or update them to an active user that's part of a valid user group that has permission to run the selected reports.
Thanks to everyone who helped with it, and I hope this is helpful to anyone else who comes across a similar situation!