InfoCube &1 was aggregated. Read request cannot be executed

What causes this issue?

Data from InfoCube &V1& is read with a filter below the last compressed
request ID &V2&. This is not possible, as the compression has removed
the request information from the data.
This situation can occur under the following circumstances:
A query has been started with data integrity 0 (up to released status).
This means the query always reads data for the InfoCube up to the last
rolled up request R1. While the query is still open and used for
navigation, a new request R2 is loaded, and the cube is compressed,
including this new request R2. Now it is no longer possible to only read
data up to the original request R1.
A query has been started that uses the delta cache. The delta cache
already contains data up to request R1, and the last request used for
reporting is request R2. Now only the data behind R1 up to request R2
needs to be read from the database, while the other data parts can be
taken from the cache. If the cube has been compressed up to a request
behind R1 in the meantime, it is no longer possible to read the
requested data from the database because it has been partly compressed.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

The read process had to be terminated.

How to fix this error?

Start the query or web application again.

Procedure for System Administrators

Consider compressing requests later. If requests have been compressed,
the query cannot refer to these requests any more for consistent query
navigation. A delay between loading requests and compressing these
requests is therefore recommended. This delay should at least cover the
longest time a query can be open for navigation within the same session.

Error message extract from SAP system. Copyright SAP SE.