Spotfire Ideas Portal
Our team was requested to create a set of schedule update to do the following:
Cache report at 6AM, reload at 11AM. They do not want a reload at 4PM.So the repeat cycle is out of the questionWe've experimented with multiple schedule during the day, so:
6AM to 11AM (no reload)
11AM to 11PM (no reload)
However in this configuration, the report first tries to unload at 11AM before reloading the report again.
This is how I would schedule this report in 6.5 (I haven't had the chance to test scheduling much on 7.9). Overlapping schedules do not cause a reload in 7.0 and below. If they do cause a reload in 7.5 and above I would consider it a bug, raise it with support. The reload should only be controlled by the "Updated every x minutes" clause. We use 1440 minutes since that's the total number of minutes in a day, so it's easier to use that than the actual minutes of the schedule line. Using a minutes value larger than the schedule line doesn't really affect the schedule line as it just means it runs once per line.
Updated every 0 minutes between 00:00 and 06:00 on Mon Tue Wed Thu Fri Sat Sun.
Updated every 1440 minutes between 06:00 and 11:00 on Mon Tue Wed Thu Fri Sat Sun.
Updated every 1440 minutes between 11:00 and 00:00 on Mon Tue Wed Thu Fri Sat Sun.
All versions (up to 7.7 that we are testing).
The problem is that with the plan listed (that can be implemented at this time), it actually unloads the report, and queues the reload at the same time. The end result something like:
11:00:00 AM (Queue unload)
11:00:00 AM (Queue reload)
11:00:01 AM (Unload report)
11:00:03 AM (Report unloaded)
... (server may be busy doing other queues)
11:05:36 AM (Load report)
This means that there is an uncontrolled gap where no report is cached, and users can hit the server at that time, and hit directly against the database.
What version is this for? Easy to do on 7.0 and below.