Package Run History

Package Run History

Skyvia logs all the package runs and allow you to view their results in details.

The result of the last package run is displayed on the Integration Packages page in the State column. A package is considered Succeeded if the most recent package run loaded all the records successfully. It is marked as Failed both if at least one record was not loaded successfully, or when the package was not able to execute completely (for example, when its connection became invalid).

packages-page-grid

On this page you can quickly see which packages executed successfully, and which failed. If necessary, you can sort and filter packages by their state.

For more detailed log open the Package Details page for the package you want to see the log of. The detailed log is displayed in the Run History pane on the right side of the page. It displays the list of the package runs, their status, and the numbers of successfully processed and failed rows. See the details below.

 

Run History Columns

 

Column

 

Description

# (package run ID)

The ID of your package run. You may specify it when contacting our support about errors in your package run.

State

The state of the package run. Can be one of the following:

Succeeded - the package successfully loaded data to target objects.
Failed - the package failed to execute.
Queued - the package is queued for running.
Running - the package is being executed.
Canceled - package execution has started but was canceled.
Canceling - canceling of the package execution is in progress.

Results

Displays the results of the package run - the numbers of successfully processed and failed rows. When you click a specific package run, the field expands and shows the numbers of successfully processed and failed rows on per-table basis. It can be different for different kinds of packages. See more details below.

Date

Displays when the package run occurred.

Duration

Displays how long the package run took.

 

How to View Older Runs

If your run history is very long, Skyvia shows only the most recent runs. You can display older runs in two ways:

Scroll down to the bottom of the Run History and click the Show more runs link. This will display more runs and you can repeat this action as many times as you need.
Click filter in the Run History header and specify the time period, for which you want to see your package runs.

run-histoy-filter

The latter option is more recommended, especially if your package runs very often and you need to view old runs.

After you apply filters, the interval start and end date and time are displayed in the Run History header.

run-history-filtered

To clear the filter, simply click the cross icon in the Run History header.

 

How to Delete Package Run History

To delete the history of package runs together with per-record error and success logs, click Actions, and then click Clear History. All package runs except for the last one will be deleted, together with per-record logs. The history and logs are also deleted when you delete the integration package itself.

 

Import Package

For import packages, the Result column displays the numbers of successfully and unsuccessfully processed rows on a per-table basis for a selected package run. If some rows failed, the number of failed rows for a table is a link. You can click this link to download a CSV file with detailed per-record error log. This CSV file contains the values of the fields from the failed rows that were used in mapping and the error description for each failed row.

For import package, the numbers of successfully imported rows for a table are also links. You can click such link to download a CSV file with the result values of the mapped target columns and the primary key of the result record.

run-history-import

 

Export Package

For export packages, the Result column displays display the numbers of exported rows on a per-table basis for a selected package run.

note Note

In export packages that export data to locally downloadable CSV files, Run History plays a special role: you download the result CSV files by clicking the number of exported rows from a table in the Run History. Please note that the result files in this case are only stored for 7 days since the package run, and after 7 days they won't be available, and you will need to perform export again. The number of exported rows from a table is a link only for the export packages that export data to locally downloadable CSV files. It is not a link for packages that export data to a cloud file storage service or FTP.

 

run-history-export

 

Replication Package

For replication packages, the Result column displays display the numbers of loaded rows on a per-table and per-operation basis for a selected package run: it displays (from the left to right) the numbers of successfully inserted, updated, and deleted rows and the number of failed rows for each table. If some rows failed, the numbers of failed rows are the links to per-record error logs for each table.

run-history-replication

 

Synchronization Package

For synchronization packages, the Result column displays display the numbers of loaded rows on a per-table and per-operation basis for a selected package run: it displays (from the left to right) the numbers of successfully inserted, updated, and deleted rows and the number of failed rows for each table and for each side - source and target. The number on the left is the corresponding number of row changes applied to the source, and the number on the right is the corresponding number of row changes applied to the target. If some rows failed, the numbers of failed rows are the links to per-record error logs.

run-history-synchronization