The Schedule tab controls how far back EaseLog reaches for history, and how often it checks Dynamics 365 for new audit data.

Open the Schedule tab

1. Select Environments in the left navigation.
2. Select the edit control on the environment's card.
3. Select Schedule.

Figure 1. The Schedule tab of the Edit Environment panel, showing Audit Log Start Date, First Execution Time, Frequency and the Initial Backlog Data Export toggle.

The settings

Setting Controls Audit Log Start Date How far back EaseLog goes when fetching historical audit data. First Execution Time The date, time and timezone of the first run. Frequency How often EaseLog checks for new data, for example Every 12 Hours. Next Scheduling Time When the next run happens. Calculated, not typed. Initial (Backlog) Data Export Whether the historical backlog is fetched in parallel time windows. See Initial (Backlog) Data Export.

Select Save when you are done.

The timezone matters

First Execution Time takes a date, a time and a timezone. EaseLog shows you the UTC equivalent underneath as you set it.

Check that UTC line. Scheduling in local time and reading results in UTC is an easy way to confuse yourself later, because the Activity Heatmap on the Operations tab is in UTC too.

Next Scheduling Time is calculated

It is First Execution Time plus Frequency. You do not set it directly. It is there so you can confirm the schedule does what you intended.

Choosing a frequency

There is a trade off and it is worth being deliberate about it.

More frequent Less frequent Audit data arrives sooner, so the Dashboard is closer to live. Fewer calls against Dynamics 365. More chance of being throttled during busy periods. Larger batches, and a longer gap before recent events appear.

If the environment often shows Throttled, Dynamics 365 is pushing back and a less frequent schedule may settle it. If it often shows Waiting for slot, there is work queued that the schedule is not giving room to run.

See Environment States: What Each One Means.

Changing the start date afterwards

Audit Log Start Date governs how far back the historical fetch goes. Moving it earlier gives EaseLog more history to collect, which means a larger backlog and a longer catch up.

Note

Changing the schedule does not lose anything already collected. It changes when EaseLog next goes looking.