Every chunk in the queue carries a status. Most of them need nothing from you. This article says which is which.

Figure 1. The Queue Overview page showing Queue Progress, the separate Audit and Details progress bars, the state filter chips and the chunk table.

The normal path

A chunk that is working correctly moves through these in order:

Status What is happening Do you need to act? In Queue The chunk is waiting its turn to start. No. Fetching Audit records are being pulled from Dynamics 365. No. Awaiting details The chunk is waiting its turn for detail records. No. Getting Details Detail records are being added. No. Completed Finished. No.

The two fetching states exist because EaseLog collects each chunk in two passes. See Chunks and Audit Windows.

A chunk waiting to start looks like this:

Figure 2. The first chunk appearing in the queue with status In Queue, its audit window and its record count.

Awaiting details is the one that looks alarming and is not. The Audit bar can sit at 100 percent while Details is still at zero. The first pass is finished and the second has not started:

Figure 3. The Audit bar at 100 percent while the Details bar is still at 0 percent, with the chunk showing Awaiting details. This is the clearest illustration of the two fetch phases.

When both bars reach 100 percent the chunk reads Completed and the environment goes back to Idle:

Figure 4. A finished sync, with both the Audit and Details bars at 100 percent, the chunk Completed and the environment back to Idle.

When something goes wrong

Status What is happening Do you need to act? Retrying Something failed and EaseLog is trying the same chunk again. It tries up to three times by itself. No. Let it finish. Failed All three automatic attempts failed. This chunk has been set aside. Yes. See Retrying Failed Chunks.

Failed does not mean stopped

When a chunk fails, the other chunks keep running. The sync continues. You lose the audit window that chunk covered until it is retried, and nothing else.

This is why the Failed chip shows a count rather than an alarm. Check it, act on it, but do not treat it as an outage.

Reading the filter chips

The chips above the chunk table group the same information:

Chip Contains All Every chunk. In Progress Chunks actively being worked on. Queue Chunks waiting to start. Completed Chunks that finished successfully. Failed Chunks that exhausted their retries.

A healthy environment that has caught up shows everything under Completed, with Failed at zero.

Note

Queue states describe individual chunks. The environment as a whole has its own separate set of states. See Environment States: What Each One Means.