After you select Complete, EaseLog starts collecting. This article shows what a healthy first sync looks like as it happens, so you can tell normal progress from a problem.

Right after connecting

The new environment appears on the Environments page with No activity yet, 0 Logs, and the state Building queue.

Figure 1. The Environments page immediately after a new connection completes, with the new environment showing Building queue and no activity yet.

Nothing is wrong. EaseLog is working out what to fetch.

Follow it in Queue Overview

Select the queue control on the new environment's card.

Building queue

The page explains that chunks will appear shortly. The table is empty and every counter is zero.

Figure 2. Queue Overview immediately after connecting, with the environment in Building queue and a banner explaining that chunks will appear shortly.

This lasts seconds, not minutes.

In Queue

The first chunk appears, with the audit window it covers and how many records it holds. Worker Started and Worker Completed are still empty because it has not begun.

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

Processing

The environment state changes to Processing with a live counter, and the chunk starts moving.

Audit finishes before Details

This is the moment that confuses people, so it is worth seeing.

The Audit bar reaches 100 percent while the Details bar is still at zero, and the chunk reads Awaiting details.

Figure 4. 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.

The sync is not stuck. EaseLog fetches in two passes: the audit records first, then the detail of each one. A completed Audit bar means the first pass is done and the second has not finished. See Chunks and Audit Windows.

Completed

Both bars reach 100 percent, the chunk reads Completed, Total Audit Logs shows the imported count, and the environment returns to Idle until its next scheduled run.

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

Your first sync is done.

Then check the data itself

1. Open the Log View from the Logs button on the environment's card. Records should be listed and Total Records should match the queue count. See Opening the Log View.
2. Open the Dashboard and select the new environment in the Environment picker. The Overview tab should show records, and Sync Completion should read 100 percent.

If something does not look right

What you see What it means Failed count above zero Some chunks exhausted their retries. The rest continued. See Retrying Failed Chunks. State reads Error Usually the connection. Check the Connection tab of Edit Environment. State reads Throttled Dynamics 365 slowed EaseLog down. It resumes on its own. State reads Waiting for slot Outside the hours you set in step 3. It starts at the next slot. Fewer records than expected Check your Audit Log Start Date, and whether auditing was enabled in Dynamics 365 for that period.

See Environment States: What Each One Means.

Note

A large backlog takes a while, and that is normal. If you want it faster, turn on Initial (Backlog) Data Export and give it generous time slots.