incorrect scheduled reports

Hi everyone,

 

We’ve had a very strange instance where some of our scheduled reports have been generated and sent out, but when people open the attachment, it’s an entirely different report from what they were expecting (some people received a sales report when they were expecting a membership report, for example).  Has anyone else experienced something like this or have any ideas what might cause it?

 

Cheers,

Kathleen

Parents
  • Thanks, everyone!  Good to know ( I suppose!) it’s not just us…

     

    Cheers,

    Kathleen

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of David Frederick
    Sent: Tuesday, 18 December 2012 6:46 AM
    To: Kathleen Smith
    Subject: RE: [Tessitura Technical Forum] incorrect scheduled reports

     

    Yes, we experienced that same problem. I have a TASK ticket opened up on the issue. For us, it seems to be related to the same report scheduled multiple times at the same time and running concurrently. One job appears to be “stealing” the output from another job.

     

    For now, we set concurrent reports to 1 and I also asked people to try and avoid scheduling the same report at the exact same time. At this point, that seems to have resolved the issue, but we’re hoping Tessitura will fix this bug soon.

     

    Thanks,

    David

Reply
  • Thanks, everyone!  Good to know ( I suppose!) it’s not just us…

     

    Cheers,

    Kathleen

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of David Frederick
    Sent: Tuesday, 18 December 2012 6:46 AM
    To: Kathleen Smith
    Subject: RE: [Tessitura Technical Forum] incorrect scheduled reports

     

    Yes, we experienced that same problem. I have a TASK ticket opened up on the issue. For us, it seems to be related to the same report scheduled multiple times at the same time and running concurrently. One job appears to be “stealing” the output from another job.

     

    For now, we set concurrent reports to 1 and I also asked people to try and avoid scheduling the same report at the exact same time. At this point, that seems to have resolved the issue, but we’re hoping Tessitura will fix this bug soon.

     

    Thanks,

    David

Children
No Data