Deactivating quantum jobs

I am not familiar with quantum per se, but i suspect you hit a typical newbie problem like most of us encountered at some stage.
Whatever you put in config/config.exs are compile time config. What you want here is run time config, which you need to fetch the config data yourself, call whatever api yourself.

Thanks for the response. Yes, I am aware of the compile time config. This is a production system and right now we cannot do a deployment. When the application is launched, it picks the config file from a specified location

/xyz/beam -config /opt/config/sys.config

The point is, this config file is read every time and it is editable. I am able to change the pool_timeout values in the configuration file and it applies when the application is restarted. However the changes made to scheduled jobs do not apply. I want to know if there is any way to stop scheduled jobs either by adding something additional to the config files or from the iex command line on the server

you can always activate and deactivate jobs runtime on server, YourApp.Scheduler.deactivate_job(:ticker) or YourApp.Scheduler.activate_job(:ticker) Only thing you need, is to set the name of your job.

YourApp.Scheduler.new_job()
|> Quantum.Job.set_name(:ticker)
|> Quantum.Job.set_schedule(~e[1 * * * *])
|> Quantum.Job.set_task(fn -> :ok end)
|> YourApp.Scheduler.add_job()

Or from config you can set this way,

config :your_app, YourApp.Scheduler,
  jobs: [
    news_letter: [
      schedule: "@weekly",
      task: {Heartbeat, :send, [:arg1]},
    ]
  ]

more