Files
Consideration
When migrating from FME Flow (pre-2025.1) to FME Flow 2025.1 or later with "Allow items to be overwritten if they already exist" enabled, the backupConfiguration.fmw The utility workspace may be replaced with an outdated version incompatible with the current REST API, causing scheduled backups to fail.
Why This Happens
FME Flow ships with a utility workspace, backupConfiguration.fmw, that powers scheduled configuration backups. This workspace makes REST API calls internally to perform the backup.
When restoring a configuration from an older FME Flow instance with "Allow items to be overwritten if they already exist" enabled, the migration process replaces the current backupConfiguration.fmw with the older version from the backup package. Older versions of this workspace used the legacy REST API v3, which was deprecated in FME Flow 2025.1 and fully removed in FME Flow 2026.1.
As a result:
- On FME Flow 2025.x: The overwritten workspace calls deprecated v3 API endpoints, causing an HTTP 404 error when the backup schedule runs.
- On FME Flow 2026.1 and later: The v3 API is no longer available, so the workspace will fail completely.
This issue does not affect fresh installations of FME Flow 2025.1 or later, where backupConfiguration.fmw is already updated to use REST API v4.
How to Resolve It
After completing your migration, manually replace the overwritten workspace with the current version bundled with your FME Flow installation:
1. In the FME Flow Web User Interface, navigate to Repositories > Utilities.
2. Delete the existing backupConfiguration.fmw workspace.
3. Locate the current version of backupConfiguration.fmw from your FME Flow installation directory (typically under <FMEFlowDir>/Server/repository/Utilities/).
4. Upload the current workspace back to the Utilities repository.
5. Navigate to Schedules and verify the Backup_Configuration schedule is still enabled and configured correctly. See Performing Scheduled Backups of an FME Flow Configuration for parameter details.
6. Run the schedule manually to confirm the backup completes successfully.
To avoid this issue in future migrations, do not enable Allow items to be overwritten if they already exist for the Utilities repository, or deselect that repository from the restore scope where possible. See Restoring an FME Flow Configuration for more on controlling overwrite behavior during restore.