SYMPTOM:
When a report is used as a filter in an element list prompt, it does not hit cache.
An example of this behavior can be setup as follows using Strategy Tutorial:


CAUSE:
This is the expected behaviour for reports as a filter in Strategy Intelligence Server 9.0.x. Reports that are used as a filter are resolved in the SQL Engine for report execution and prompt element browsing - and the report is never actually executed as a report instance so no matching cache can be hit.
ACTION:
The Intelligence Server product is behaving as designed. Reports as a filter cannot use a cache in another report instance execution.