Whenever we cancel a running job (in our case: using the REST API), the job is cancelled successfully on the FME Server core (the job reports itself as aborted when we fetch the status), but the engine on which the job is running (on a different physical machine than the Server core) just keeps on going: the job simply runs until the end of the translation. This is not what I expected, but since I don't see any errors in the server logs e.g. about communication issues with the engine, I started to wonder.
Is this intended behaviour? If so, are there ways to actually stop the job process on the engine as well? If not, any suggestions on how to fix this?