Resolution: Cannot Reproduce
When a Compute Engine task that deals with an analysis report is interrupted, the task is automatically restarted and, after several unsuccessful attempts, canceled (see
It works fine when the task is interrupted before all the changes are persisted in the Database and before the corresponding data start to be indexed into Elasticsearch. Replaying the task will produce the same effects.
But if a task is interrupted while indexing the corresponding data in Elasticseach, if the indexation of a project analysis is incremental, the task can't be simply played again. And, as a consequence, some inconsistencies may remain between Elasticsearch and the Database.
If the indexation of a project fails or is interrupted, the Compute Engine could first index the whole project just before computing the following analysis.