Queue Overview tells you whether EaseLog is keeping up with an environment, what it has already brought across, and whether anything failed.

Open Queue Overview

1. Select Environments in the left navigation.
2. Select the queue control on the card of the environment you want to check. It sits between the record count and the delete control.

Figure 1. The Environments page showing one card per connected environment with its idle state, record count, queue and delete controls.

What the page shows

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

Queue Progress carries the environment's current state, for example Idle until 08/26/2026, 8:00 PM. See Environment States: What Each One Means.

Next to it are two progress bars, and they are not duplicates:

Bar Tracks Audit The audit records themselves being fetched from Dynamics 365. Details The detail of each record being added afterwards.

EaseLog fetches in those two passes, so a sync can be complete on Audit and still working on Details. Both need to reach 100 percent before an environment is fully caught up.

Total Audit Logs shows how many records EaseLog holds for this environment.

The state filters

Below the progress bars are filter chips, each with a count:

All, In Progress, Queue, Completed, Failed.

Select one to show only the work in that state. Failed is the one to check first when something looks wrong.

The chunk table

EaseLog does not fetch an environment's history in one go. It splits the work into chunks. One row is one chunk.

Column Tells you Audit Window The period of time this chunk covers, as a start and an end. Status Where this chunk has got to. Progress How far through it is. Worker Started When work on it began. Worker Completed When it finished. Records How many audit records it brought across.

The footer shows how many chunks there are in total.

See Chunks and Audit Windows for why the work is split this way.

Pause

Pause in the bar at the top stops the queue for this environment. See Pausing and Resuming a Sync.

Note

An environment that reads Idle with everything at 100 percent is healthy. Idle means there is no work to do right now, not that something has stopped.