Sometimes a chunk cannot be fetched. This article explains what EaseLog does about it on its own, and what is left for you.
Read this first
A failed chunk does not stop the sync. The other chunks carry on. What you have lost is the one audit window that chunk covered, until it is retried.
So a Failed count above zero is worth acting on, but it is not an outage.
EaseLog retries by itself first
When a chunk fails, EaseLog does not give up. It retries the same chunk automatically, up to three times. While that is happening the chunk shows as Retrying.
You do not need to do anything during that. Let it finish.
Only when all three attempts have failed does the chunk move to Failed and wait for you.
Find the failed chunks
- Open Queue Overview for the environment. See The Queue Overview Page.
- Select the Failed chip above the chunk table.
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 table now shows only the chunks that need attention, with the audit window each one covers.
Retry them
Use Retry on a single chunk, or Retry All to put every failed chunk back into the queue at once.
A retried chunk returns to In Queue and runs from the beginning, through Fetching, Awaiting details and Getting Details, exactly as it would have the first time.
If they fail again
Repeated failures across many chunks usually point at the environment rather than the chunks. Check the environment's state:
- Error suggests the connection settings need correcting. Check the organisation URL and credentials on the Connection tab of Edit Environment.
- Storage full means there is nowhere to put the data. Clear older data or raise the limit.
See Environment States: What Each One Means.
Tip
Make checking the Failed count part of your routine. Retrying a handful of chunks takes seconds, and it keeps the audit trail complete. A gap in an audit trail is only a problem at the moment somebody needs it.