Capturing is half the job. This is the half where the data reaches whoever needs it.
What comes out
Cloneable produces your data in several shapes, and which you want depends on who receives it:
KMZ, for mapping tools. This is the big one, because it can carry your field imagery inside it. With images included, expect a large file.
GeoJSON, for mapping and analysis tools that prefer it.
A zip archive of a job.
CSV, for spreadsheets, from your jobs list.
A bulk pole inspection package, when you want inspection output across a batch rather than one job.
Exports scoped to one job take the job's name by default (with spaces and punctuation turned into dashes), and the person exporting can change the name before downloading. A name stamped with a date and time uses your local time. The jobs list CSV is the exception. Its date is the universal (UTC) date, which may not match your local calendar date.
Where exports are started from
It depends what you export, and the starting point sits with the item itself rather than in one central place. You export a job's data from the job, and a jobs list from the list.
If your organization sends data to Katapult or to ArcGIS automatically rather than by hand, your organization switches that on per configuration, and it is a separate thing from downloading a file. See Set up your configuration, stage by stage.
Watching one run
Open Exports from your dashboard, where the status card tells you what is happening now. An export in progress says so and gives you a count, and there is a refresh if you would rather not wait.
An in-flight job also shows up on your dashboard with a relative time, and offers to take you to the map to see what is arriving.
Two things that look wrong and are not
Older exports disappear from the status card. It only reports recent activity, over the last seven days. An export from last month not appearing there does not mean it did not happen.
Two places can show you different numbers. The summary counts only cover the last seven days, on your dashboard and in the exports view alike. The exports view's list of issues is not limited that way, so an older issue can appear in that list without being counted in either summary. That is the expected relationship between them rather than a contradiction. When they disagree, work from the list of issues, and see When an export does not finish for what its own count does and does not include.
Checking it actually worked
The file arrived, and is not suspiciously small. A KMZ with images included is large. A tiny one usually means the images were left out when it was exported, or that the data was not there, rather than that the export failed.
Open it once in whatever will consume it, before sending it on. You want to find that a file downloads and will not open before your client does.
The exports view shows no issues for that job. See When an export does not finish.
Cloneable says "issue", not "error"
Worth knowing so the wording does not throw you. Where Cloneable records a failed export, it calls it an issue, and the export views use that word consistently. It does not mean something less serious than an error. It is just the word.
If the export link does not seem to do anything
That is a different problem with its own article. See My export link does not seem to do anything.