FME Version
Known Issue ID | FMEFLOW-24135 |
---|---|
Discovered | FME 2023.0 |
Affects | FME 2023.0+ |
Resolved | Unresolved |
Symptom
When migrating from an FME Flow version that uses Schedule Categories (pre-2023.0) to a version using Schedule Tags (2023.0+), categories will not automatically convert to tags. This also applies when importing an FME Flow project from a version prior to 2023.0.
Cause
Before 2023.0, the Schedules page used the V3 API. In 2023, it was upgraded to use the V4 API, which replaces the concept of categories with tags. As a result, when projects or backups are uploaded to versions 2023.0+, schedule categories are dropped since they no longer exist.
Workaround
The V3 API remains backwards compatible with projects and backups uploaded to versions 2023.0+. The V3 endpoints, such as GET /schedules/{category}/{name}, GET /schedules/categories, and GET /schedules, can still access schedule categories. It is possible to create a workspace that utilizes both the V3 and V4 endpoints to replace each schedule, uploading its category as a tag.
Support
For help with workspace creation or any questions, please contact Safe Software Support.
Comments
0 comments
Please sign in to leave a comment.