Skip to content

Retrying an Import

Overview

If an import job fails or completes with unexpected results, you can rerun the import job using the "Rerun Job" option. This creates a new import job with the same configuration and source data location as the original import.

The "Rerun Job" feature is available for imports initiated from both external storage and local uploads (from "My Computer").

Instructions

Rerunning an Import Job

To rerun an import job:

  1. Open the Flywheel Core Web App.
  2. Navigate to the destination Project where the original import was run.

  3. Navigate to the "Imports" tab of the destination Project (in the overflow menu).

    Project -> Imports Tab

  4. Locate the import job you want to rerun in the list.

  5. Click the overflow menu (three dots) on the import job line.

    Project -> Imports List -> Job Overflow Menu

  6. Select "Rerun Job" from the menu.

  7. Confirm the action in the dialog that appears.

A new import job will be created and started immediately with the same settings and source data location as the original import job. The new import job will appear as a separate entry in the Imports list.

Limitations

Local Uploads - Data Availability

For imports that were initiated by uploading data from "My Computer", the "Rerun Job" option is only available while the uploaded data remains in temporary staging storage.

If the staging storage has been cleared (for example, because the data was already successfully imported or the data expired and was removed), the "Rerun Job" option will be disabled.

When disabled, a tooltip will explain why the option is unavailable and what steps you can take:

This import job cannot be rerun, because the source data is no longer available. The source data may have already been imported successfully or it may have expired and been removed. To rerun this import job, the source data will need to be re-uploaded.

In this case, you will need to restart the import process by re-uploading the source data from your local machine.

CLI-Initiated Local Uploads

For imports that were started using the Flywheel CLI with local file uploads, the import begins while files are still uploading to optimize the experience.

These CLI-initiated imports cannot be rerun from the Web App. The "Rerun Job" option will be disabled with a tooltip explaining:

This import job cannot be rerun from the Web App. It must be resumed using the Flywheel CLI from the machine on which it was originally started.

To resume or retry a CLI-initiated import, use the Flywheel CLI on the machine where the original upload was started.

External Storage Imports

For imports from external storage, the "Rerun Job" option is available as long as:

  • The external storage registration still exists in Flywheel
  • The source data files are still present at the original storage location
  • You have appropriate permissions to access the external storage

Common Use Cases

Fixing Configuration Errors

If an import completed but used incorrect mapping rules or settings, you can:

  1. Cancel or wait for the original import to complete
  2. Adjust the import configuration if needed
  3. Use "Rerun Job" to start a fresh import with corrected settings

Recovering from Failures

If an import job fails due to:

  • Temporary network issues
  • Service interruptions
  • Storage access problems

You can use "Rerun Job" after resolving the underlying issue to retry the import without needing to reconfigure everything.

Importing Updated Data

If the source data has been updated or corrected at the external storage location, you can use "Rerun Job" to import the latest version of the data.

Note

For local uploads, the "Rerun Job" option uses the originally uploaded data, not new data. To import updated local data, you must start a new upload and import.

Next Steps