Sometimes data does not make it out. Cloneable keeps a list of exactly which objects failed and why, and it is more helpful than most error screens.

First, the word

Cloneable calls these issues rather than errors. Same thing. It uses the word consistently, so that is what to look for.

Where to look

Open Exports from your dashboard. As well as the status card, that view keeps a list of export issues.

Work from that list. The summary counts only cover the last seven days, on your dashboard and in the exports view alike. The list of issues is not limited that way, so the two can honestly disagree. When they do, start from the list. See Export your data.

Read the product's own explanation first

This is the part worth knowing about.

Open an issue and Cloneable gives you what happened and what you can do, written in plain language rather than as a raw error. The same detail also gives you the technical message, the object's own reference, and the execution logs.

Start with those first two sections. They are Cloneable's own account of the failure and its own suggested fix. When Cloneable recognizes the failure, they are more specific than anything a general guide could tell you. The raw message is for us, not for you.

If what you can do does not resolve it, that is the point to contact us rather than to keep retrying.

Narrowing a long list

Filter by job, which is the useful cut when one job's export went wrong and the rest are fine.
Sort newest or oldest first, depending on whether you chase something that just happened or work through a backlog.
Search by the object's reference. Note that search matches that reference only, so searching for a job name or for words from the error will find nothing. Filter by job instead.

An issue that is tied to a specific object carries a copy control for that object's reference. That reference is the single most useful thing to send us, because it identifies exactly which object failed rather than approximately which export.

Two things about the count

The count on the issues list is not a fixed total. By default it counts issues still outstanding, and it switches to counting everything once you include resolved ones. So two people looking at the same organization can honestly report different numbers.

Say which you look at when you quote a figure to a colleague or to us.

If the list is empty

An empty list means no outstanding export issues, which is the good outcome. Cloneable hides issues someone has already marked resolved by default, so turn on Show resolved before concluding that nothing ever failed. If the list is empty even then and data is missing, the export did not fail. Look at whether the data was there to export in the first place. See Review what your crews captured.

What to send us

The object reference, copied from the issue, if the issue has one
What the "what happened" section said
Which job it belongs to
Whether it has happened before, or whether this export used to work

That is usually enough for us to answer without a call.

When an export does not finish