History

The History tab gives users visibility into all past Export and Import operations initiated within the platform. It provides a searchable, filterable log with status indicators and context-specific actions to help you manage your bulk metadata workflows effectively.

Only users in the Owner group can access the Export/Import feature.

What is shown in History

Every time a user performs an Export or Import operation, a new entry is logged in the History tab with the following metadata:

Field	Description
File Name	Name of the CSV used or generated during the operation.
Operation	Indicates whether the operation was an Export or Import.
Type	The type of object involved: Catalog (dataset), Catalog (non-dataset), Glossary, or Policy.
Created At	Timestamp when the operation was triggered.
Status	The result of the operation: In Progress, Success, or Failed.
Action	Available actions depending on the operation status (explained below).

Status:

• In Progress -> Operation is running in the background.

• Success -> The operation completed successfully.

• Failed -> The operation could not be completed due to an error.

Available Actions by Status

Operation Type	Status	Available Actions
Export	Success	✅ Download CSV of desired export
Export	Failed	❌ Retry Export (if supported) ❌ View error tooltip
Import	Failed	❌ Download error report
Import	Success	✅ Review changes in platform UI ✅ Download CSV of file used in import
Export/Import	In Progress	⏳ Progress indicator, no actions

The following describe the actions available when Export/Import operation is Failed.

Retry Export

If the export operation failed:

• The status will be marked as Failed.

• A tooltip icon will appear beside the status. Hovering over it will show the error message (e.g., timeout, unknown error).

• You will see a Retry Export button in Action, which allows you to re-trigger the same export without needing to reconfigure everything.

Download Error report

• No changes will be executed on the platform in import fail.

• The error report is the same CSV file the user uploaded, but it includes inline error messages for each failed row.

• Example: If row 10 had an invalid attribute, that row will be marked with the corresponding error.

• You will need to fix the rows with errors and before attempting another import operation with the same file.

Filters and Search Behavior

To help locate specific operations, you can use:

• Search bar — search by file name

• Filters — click on “Apply filters” to narrow results by:

  • Operation type (Import or Export)

  • Object type (Catalog (dataset), Catalog (non-dataset), Glossary, Policy)

  • Status (In Progress, Failed, Success)

  • Created at (select a date)