The SystemExit issue you’re seeing is typical with Click, as it’s designed for standalone CLI applications and automatically calls sys.exit() after running a command. This behavior can trigger SystemExit exceptions in non-CLI environments, like Databricks notebooks or task workflows, where an exit might be interpreted as an error.

• Which Databricks Runtime Version is being used, and does it match your local Python version?
• Are you running this Click command as a scheduled job, a triggered job, or manually in a notebook?
• Is the Click application using a single command or multiple nested commands?
• Do any Click options have default values or callbacks that might behave differently across environments?
• When running in Databricks, does the task log show a complete run before the SystemExit error, or is the error interrupting the task?
• Have you tested different Click settings, such as setting standalone_mode=False in the Click function, to see if behavior changes?