I will try to do this after the easter, but I believe the sample workspace won't get triggered so I won't have any logfile to examine.Cause I did try to run different workspaces and none of the got triggered by the workspace protocol only with push protocol.
For the hack, I had too rename the file after read so that it didn't use the same file for all the workspaces lined up in queue.
So what I have debugged so far is that when I register the workspace for notification when uploading a workspace, the subscription is registered as a push protocol the workspace gets triggered when the topic triggers, but without any topic message.If I upload the workspace and only register it with the job submitter, and then manually create a new topic, new publication and a new subscription with the workspace protocol the workspace does not get triggered.The json file get produce every time.I could try and hack this to look for the last json (Cause this is the only notification job running on that server), and dont care about the missing topic message.
Hi@paalped,
Sorry your having this issue.It be worth testing to see if other topics are behaving the same or if its just isolated to this one topic if its isolated to one topic I might be inclined to create a new topic.If all topics have the same behavior it is probably a disconnect between the core and engine in particular ports 7072 - 7076.It might also be worth checking to see if the json file is being written.Usually its placed in the C:/ProgramData/Safe Software/FME Server/resources/system/temp/subscriptions where C:/ProgramData/Safe Software is your fmeServer file share.Feel free to create a case if you need a hand debugging.