Hello @VZLA ,

I am having the exact same problem. Here is the answer for your questions:

- Which Databricks Runtime Version is being used, and does it match your local Python version?
I am using 15.4 LTS (includes Apache Spark 3.5.0, Scala 2.12) runtime

- Are you running this Click command as a scheduled job, a triggered job, or manually in a notebook?
A triggered job using DatabricksSubmitRunOperator

- Is the Click application using a single command or multiple nested commands?
The command is brt evaluate --config /path/to/config --set some.value.changed.to=2

- Do any Click options have default values or callbacks that might behave differently across environments?
As long as I can tell, it doesn't.

- When running in Databricks, does the task log show a complete run before the SystemExit error, or is the error interrupting the task?
The error does not stop the task, which actually executes successfully. It happens right after the task finishes.

- Have you tested different Click settings, such as setting standalone_mode=False in the Click function, to see if behavior changes?

This is how my cli.py __main__ is implemented:

if __name__ == "__main__":
    cli(standalone_mode=False)