Hi @NavyaSinghvi ,
Thank you for clarifying that. I believe I was able to replicate the issue you're describing and was able to circumvent it by adding `job.trigger.file_arrival.location` as a task-level parameter, and not as a job-level parameter.
![brockb_0-1719977522755.png brockb_0-1719977522755.png](/t5/image/serverpage/image-id/9159i2904165F44B5D274/image-size/medium?v=v2&px=400)
Can you please give that a try and let me know how it goes?
Thank you.