Skip to main content
  • EN

I am trying to create an automation using a trigger that watches a directory. If a file in the directory is added/created it launches an FME Workspace. However I keep getting the following error:

2024-12-14T20:10:08Z | 410109 : (Automations) Creating link from trigger...
3	2024-12-14T20:10:08Z | 410108 : (Automations) Creating dirwatch trigger...
4	2024-12-14T20:10:08Z | 410112 : (Automations) Unable to assemble automation. There was an issue with component "Trigger". Publisher dirwatch does not exist.

The same thing happens when I try add a trigger that watches an FTP? and I get the same error when trying to add a Publication under the Notification.

What am I missing? Do I need to add something special for a trigger to work? is it possible that I am missing some part of FME?

I am working with a FME FLOW 2024.1that is in a Azure Kubernetes cluster.

Any help or hint that could explain the error is highly appreciated.

I am working with a FME FLOW 2024.1that is in a Azure Kubernetes cluster.

This most likely is somehow related I would guess. 

Are you able to set up a directory watch or FTP watch in the old fashioned way (e.g., Notifications(classic), Publications)? If you set up the publications you might see some more information in the specific publication logs (logs>core>current>publishers>dirwatch.log).

It’s also possible some ports are closed. You can see more info on ports here: https://docs.safe.com/fme/html/FME-Flow/ReferenceManual/FME-Flow-Ports.htm
 

Setting up a directory watch or FTP watch in the old pattern that will give you solution.

Reply


Community Stats

30,351
Posts
115,336
Replies
38,078
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.