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.

Can you please give that a try and let me know how it goes?

Thank you.