We have a report that takes a very long time to run (no way to optimize) and the user cannot wait for it, so it must be cached. My problem: The data pull runs at :20 after, finishes at about :40. The cache is flushed at say :50, but the cache takes a while to swap, say from :50 to :60. Is there no way to trigger the swap after the cache is flushed?
Doesn't the user run the risk of opening the report and having to wait: (:45 - :60) It doesn't make sense (for me) to have the cache flushed, then swapped. Am I missing something?
FYI I use a subscription to swap the cache for 12 different parameter values (languages). The reports display an unual amount of text, thus the length.
Any help appreciated,