-Because while the new data coming from httpCaller should be written to AttributeFileWriter, first the file starts the parse process. In this case, it causes old data to be processed instead of new data.
-If I delete this file from desktop then run the workflow from fme server;
-Fme server run workflow and see engine logs;
Why do it works first parsing file then httpCaller ?
True way that is it gets httpCaller new data firsly and write to file.
On FME desktop if you are running with caching on then the HTTPCaller will not run again - if you turn off the caching it will run the whole process on FME Desktop including the HTTPCaller. For FME Server are you sure that the FME Server has access to your Desktop? is it running on the same machine as the FME Desktop?
Thanks for your answer
I did not delete that created file on desktop for this scenerio as you see picture it access file and parse,
-FME Server and FME Desktop are running on the same machine.
I turned off the caching. Actually, it working correctly on FME desktop (httpCaller gets updated data and write file)
On the other hand, I tried work on FME Server,
httpCaller gets updated data it s good but did not write update data in this file. It gets old data from file.
Thanks for your answer
I did not delete that created file on desktop for this scenerio as you see picture it access file and parse,-FME Server and FME Desktop are running on the same machine.
I turned off the caching. Actually, it working correctly on FME desktop (httpCaller gets updated data and write file)
On the other hand, I tried work on FME Server,
httpCaller gets updated data it s good but did not write update data in this file. It gets old data from file.
Unless you've configured it otherwise, FME Server runs using a seperate Windows User account. As desktops are just a folder under a user account, it is quite likely that the FME Server account does not have permission to access the desktop for the account that you login with.
Yes you are right. I use https://docs.safe.com/fme/html/FME_Server_Documentation/AdminGuide/Running_System_Services_Under_Different_Accounts.htm
link and fix it. Thanks @hkingsbury