Upload History shows every CSV file you have sent to Kintsugi, what happened to it, and which rows did not make it in. Use it to confirm an upload finished, to see how many transactions were saved, and to download a file of the rows that need fixing.
Upload History is part of the File Upload tab on the Data Sources page. It stays on screen at all times, so you can check a past upload without leaving the page or losing your place in a new one.
Time required: 2 minutes
You will need: Kintsugi account and at least one completed file upload
Log in to the Kintsugi.
Go to Data Sources.
Go to the File Upload section.
The upload area sits at the top of the tab. Upload History sits below it.
Find your upload in the Upload History table. Uploads are listed newest first, so the file you sent most recently is at the top.
Navigate to the Status column. Status tells you whether Kintsugi is still working on the file, finished it cleanly, or finished it with rows left behind. See "What each status means" below.
Filter by Source when the list gets long. Use the filter on the Source column header to narrow the table to one data source.
Column | What it tells you |
|---|---|
Name | The file name as you uploaded it |
Source | The platform the data came from, taken from the |
Date | When you submitted the upload |
Status | Where the upload is in the process, or how it ended |
Total Rows | How many rows Kintsugi read from your file |
Persisted | How many transactions were saved to your account |
Failed | How many rows were not saved. Click the number to download the error file |
Status | What is happening | What to do |
|---|---|---|
Validating | Kintsugi is checking the file for formatting and missing fields | Wait. The status updates on its own |
Validation failed | The file could not be read, usually a format or encoding problem | Re-export your file as UTF-8 CSV from the Kintsugi template, then upload again |
Importing | The file passed validation and transactions are being saved | Wait. The status updates on its own |
Complete | Every row was saved | Nothing. Your transactions are in |
Complete with errors | Most rows were saved, some were skipped | Download the error file, fix the flagged rows, and upload the corrected rows |
Failed | No rows were saved | Download the error file to see why, then upload again |
Upload History covers file uploads only. Transactions that arrive through a connected integration such as Shopify or QuickBooks do not appear here
Each upload is a separate row. Retries are not linked to the original attempt
You cannot delete an upload or remove it from Upload History
Removing an uploaded transaction is a separate task. Re-upload the row with the same transaction_external_id and set operation to ARCHIVE
Uploaded transactions stay in Kintsugi. They do not sync back to the platform the data came from
The counts shown are for your reference. The transaction records themselves are the source of truth if a count ever looks off
Upload History shows uploads made by anyone in your organization, not only your own
Q: Why is my Persisted count lower than my Total Rows?
A: Some rows were skipped, either because they failed validation or because they could not be saved (a duplicate transaction ID, for example). Click the Failed number to download the error file and see which rows and why.
Q: How long does an upload stay in Upload History?
A: Uploads remain listed for the life of your account. There is no automatic cleanup.
Q: My upload has been Validating for a while. Is something wrong? Larger files take longer to check. If the status has not moved after several minutes, reach out through the chat bubble and include the file name and upload date.
Q: Do I need to upload again if I chose to skip the errored rows?
A: Only if you want those validated rows in your account. The rows you skipped were never saved, so upload the corrected version when you are ready.
For further concerns, we're always here to help. If you can't find the answer you're looking for, just reach out to us using the chat in the bottom right corner of your screen.