Can you provide the job log of the process, as this should detail the locations you mentioned in it. So it would be good to see that, so that we can decipher what it is doing.

That you for the quick response. The job log is attached. 

Thanks.

So if you look at line 20 are all the parameters that are being passed to the process. I don’t see any output locations in here. So I assume you have instead hardcoded those locations into your writer, rather allowing a destination to be passed into the process?

So the file gdb should be getting written to the hardcoded value that you have in your writer. So you are hardcoding that value into the process?

Here is a screenshot of the the writer’s output in this workbench. Does hardcoded mean that I give it a path instead of just a name?

Thanks for the screenshot, as that explains the problem. 
 

It shows that you have linked it to the parameter “FME_DATA_REPOSITORY”. In FME Flow that parameter is held as a fixed value in FME Flow. So no matter what you pass that parameter it will not change. https://docs.safe.com/fme/2018.0/html/FME_Desktop_Documentation/FME_Workbench/!Transformer_Parameters/FME_Server_Parameters.htm

From your workspace log starting on line 20, you can see that:

FME_DATA_REPOSITORY' `F:/FME Server System Share/resources/system/temp/upload/

So that where you have been writing to.

So it would be best to create a new parameter (Let’s say ‘A’ for an example) and link that new parameter to that File Geodatabase location.

Then you can pass in the appropriate value as ‘A’ When you are calling the job to run.