Hi ResponsiveHedgehong88 , let me see if I get it straight, you have a my_config.yaml in your repo. Then you do something like task.add_configuration(my_config.yaml) and have it logged as a config object, then you modify the config object and rerun (so now it takes the configuration from the configuration object you modified in the UI, rather than the file in the repo). Am I understanding the setup correctly?

If so, what do you mean by "is there a way to reference this file to my process"?

Hi, thanks for the answer. Loading manually set params is fine as you have explained, but I would need the file reference as well. The thing is, I'm using both the config file contents (params) and the file path (re-loading some params in other processes that don't share all the resources).
Does what you are saying mean that the file I have modified in the app overrides the existing file under the same file name in repo clone on my training instance?

Hi, what we do is indeed override the configuration so instead of taking the info from the file, we take from the input from the UI. If you're using the content of the file in other places directly, you might end up with different results.
If you can have a short code snippet to show me how you're reading \ tracking the file, I can maybe better help and provide a suggestion of what can be done!