Known Issue: FME Flow Packages and Linked Custom Transformer

Issue

FME Flow (formerly FME Server) fails to extract the package into Resources > Engine > Packages after running a workspace that contains a linked custom transformer with an FME Package. You may find this error in your job log: Python Exception <ModuleNotFoundError>.

Cause

When a package is published, the .fpkg file gets uploaded to Resources > Engine and the first time a workspace is run that contains a component of this package, it will extract the contents of the .fpkg and distribute it across a series of subfolders within Resources > Engine > Packages. This extraction process does not complete successfully when the package is within a linked custom transformer. 

Workaround

Embed the custom transformer in the workspace and run on FME Flow to extract the package files properly. Once the package files are extracted successfully into Resources > Engine > Packages > <build>-<os>, edit your workspace to have the custom transformer linked once again and republish back to FME Flow. Publish the custom transformer into the same repository. When you run the workspace, FME Flow should be able to reference the module and run successfully. 

Troubleshooting

If the suggested instructions do not resolve your problem, please contact Safe Software Support for further troubleshooting.