Activity: the sync log

The “Activity” page shows what the service did, file by file: downloads, uploads, moves, items sent to the trash, conflicts and errors. It updates live, and its content exports to CSV or JSON.

The window

At the top, three filters: “All”, “Conflicts” and “Errors”. On the right, the Export… button and the Refresh button.

Each line of the log carries an icon for the kind of event, the path of the file (relative to the account's local folder), a detail, and the time. Today's events show the time alone; older ones add the date. Events of all accounts are mixed, newest first.

Icon	Event	Detail shown
arrow down	file received from the cloud	its size; for a Google document, a mention of a link to the online document
arrow up	file sent to the cloud	its size
arrow right	file moved or renamed	its previous location
trash	file sent to the trash	on which side
warning triangle	conflict	the version kept as a copy, see Conflicts
error circle	error	the message, as Google or the system gave it
information	service event	for instance the result of an index rebuild

When the list is empty, the page shows “Nothing to report” and “Transfers, conflicts and errors will show up here.”

Clicking the “Status” line of an account that carries a badge, on the “Accounts” page, opens this page directly: “Conflicts” filter on the oldest open conflict, or “Errors” filter.

Following a transfer

A large file (from a few megabytes) appears during its transfer with a progress bar and a percentage, updated in place. When the transfer completes, the same line becomes a download or an upload; if it fails, it becomes an error. With several simultaneous transfers, each file keeps its own line.

Step 1: filter

“All” shows every event.
“Conflicts” keeps only the conflicts.
“Errors” keeps only the errors.

The page shows at most the last 300 events; the service keeps 5,000 per account, which the export returns. Refresh reloads the list from the service.

Step 2: export

Click Export…, then “Export as CSV…” or “Export as JSON…”.
The “Export activity” window proposes a dated file name, such as htkcloudsync-activite-tous-2026-10-12.csv; choose the location and save.
A message gives the number of events exported, with the Open folder button.

The export covers all accounts and follows the current filter: with “Errors” active, only the errors are exported.

CSV: one line per event, with date, account, level, kind, path and detail columns, separated by semicolons. The file opens directly in LibreOffice Calc or Excel, accented characters included.
JSON: a list of objects, one per event, with the same information.

Step 3: clear the log

The log limits itself to the last 5,000 events of each account. To start again from an empty page, click Clear the activity log…, next to Export…. The “Clear the activity log?” question reminds you that the events of all accounts are removed from this computer; the default button is Cancel, Clear confirms, and the “Activity log cleared” message appears.

Your files and your cloud are not affected, and the conflicts still open remain counted on the “Accounts” page. Export the log first if you want to keep a record.

What an export contains

The paths of the synced files, the account's address, the kind and level of each event, its date and its detail: a size, the name of a conflict copy, or the error message as Google returned it. Never the content of a file, never your sign-in. An error message from Google may quote the internal identifier of the item concerned.

The file stays on your computer, where you chose. Nothing is sent anywhere; you pass it on yourself, for instance to support with a ticket.

Note: the command line also exports the log, with date bounds and a level filter; see Command line.