Querying task details... too quickly??

We are on Appian 24.1.

I have a process model with a user task followed by a write to a RecordType.  The RecordType keeps track of task performance (i.e. how long it takes users to complete the user task) for long-term trending and reporting needs.

An expression rule is called to retrieve the details once the task completes.  This rule uses queryProcessAnalytics to pull the data for the particular task in question (processId and taskId filters).  The report filters for only completed tasks

a!localVariables(
  local!rawData: a!queryProcessAnalytics(
    report: cons!XX_COMPLETED_ACTIVITY_REPORT,
    query: a!query(
      pagingInfo: a!pagingInfo(startIndex: 1, batchSize: 5),
      logicalExpression: a!queryLogicalExpression(
        operator: "AND",
        filters: {
          a!queryFilter(
            field: "c8",
            operator: "=",
            value: ri!processId            
          ),
          a!queryFilter(
            field: "c7",
            operator: "=",
            value: ri!taskId            
          )
        }
      )
    )
  ),
  local!taskData: if (rule!XX_AnyArrayItems(local!rawData.data), local!rawData.data[1], {}),
  'type!{urn:com:appian:types:XX}XX_TaskMetrics'(
    processId: index(local!taskData, "c8", null),
    taskId: index(local!taskData, "c7", null),
    taskName: index(local!taskData, "c0", null),
    startTime: index(local!taskData, "c3", null),
    queueTime: index(local!taskData, "c9", null),
    workTime: index(local!taskData, "c10", null),
    completedTime: index(local!taskData, "c11", null)
  )
)

Now, this has been working just fine for over a year.  But recently, we saw an instance where Save Task Performance failed due to missing data (Task Name was null). 

NOTE:  The issue occurred on a Friday; it was noticed on Monday.  After investigating what we could (not a lot), we re-started Save Task Performance and it ran just fine.... found the task, created the record, and there was much rejoicing.

{

  speculation:  "It appears as if the part of Appian that marked the task as complete was lagging behind and Save Task Performance ran before the task completion was marked internally...  The task wasn't found by the report since it wasn't marked complete yet and thus the expression that builds the record had no data to include"

}

Is this possible?  Is there something else that might explain why queryProcessAnalytics failed to find the completed task information?

Thank you.

This is a single-server, on-premises Appian environment.