What is a cached service?

A user might review evaluations and find that for some of them, the services show “cached” instead of “executed” (see image below).

 "Executed" indicates that the data services were called to return new responses for the evaluation. "Cached" indicates that the data services were not called, but rather cached responses from the data services were used for the evaluation. If the PII data on the evaluation hasn't changed, the most efficient method is to use the cached response we got back from the data service so an extra API call doesn’t have to be made, unless necessary. 

Responses are cached for 30 days after a data service is executed for an entity or unique combination of PII. The cache will be used by default for any reruns of the same entities through the same workflow.

If multiple evaluations are submitted within minutes, but the PII for every evaluation has changed, the result will be executed data.

If it was the same entity, the expected behavior is for the data services to be called again (“executed”) in scenarios where the PII data is changed. We would expect the data service to not be called again in scenarios where the supplied PII does not change and the evaluation is run again within 30 days.

The cache can be refreshed to prompt the data services to execute in order to return new responses. See our guide on: Refresh Cache for Evaluation Rerun