(This is basically a scaled-down version of T157231/T192870, though it does not require developing a new type of query engine)

Users may not only want to see the results of a query, but also see how the result sets evolve over times (see T290961#7352669 for a particular use case). This is a general idea containing two possible versions:

• When users can save query and transclude the result on-wiki (T67626: [Epic] Support for queries on-wiki (automated list generation)), user can also save a "snapshot" of the query result (similar to history of Listeria page, but it is structured and machine-readable).
• On the other hand, if we use an external system to save query results (T104762: Setup sparqly service at https://sparqly.wmflabs.org/ (like Quarry but for SPARQL)), the thing to do is simple - allow a query to be rerun and all history be preserved. Quarry currently does not preserve historical results of rerunned queries.

In both cases, a scheduler is useful, for example we want a query to be run once every day/week/month.
Both are depending on softwares/services that do not currently exist, so this task is currently not actionable.