Normal 0 false false false MicrosoftInternetExplorer4
We just noticed this today. If we modify a performance time in Tessitura, like changing a performance from 8pm to 8:30pm, the change immediately is reflected on the web performance detail page, as it should, but the change does not update on the web calendar. It appears that the calendar does not sync with our servers at all. Any ideas where to start checking?
Hi Randal,
The calls that the calendar uses might be caching data (many of the performance data API methods do), so it may take 10 or 15 minutes for the change to be reflected. If the data doesn’t change after waiting a while then I suggest opening a help ticket.
Kevin Sheehan
Documentation & Learning Resources Specialist
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com
You can also reset the cache, as we typically do when important performance information is changed (keywords are especially critical, those can be cached for an hour, I think).
You can do this by:
"Touching" (changing the modified date) the Web.config file on the API (not web) server. Add a space at the end of a line, save, delete the space, save. Or use "touch" if you have unix tools installed.
Run the new terrifyingly-named API method for this purpose: DestroyCache.
The web server was inadvertently set to PST instead of ARIZONA TIME during a recent web server update. Darn daylight savings time!