Command run-now Invalid Token

[Edward-Francis-ZPG]

Describe the issue

I have a Databricks job that takes 90 minutes to run and is being triggered by a databricks jobs run-now xxxxxx --timeout 120m0s command. After exactly 1 hour, I receive a "Invalid Token" token error. I can only assume the token is not being refreshed automatically.

Steps to reproduce the behaviour

1. Run databricks jobs run-now xxxxxx --timeout 120m0s
2. Wait 1hr and see "Invalid Token" token error.

Expected Behaviour

The run-now command refreshes the token and proceeds to wait for the given timeout.

Actual Behaviour

Auth token does not appear to be refreshed causing the run-now command to error.

OS and CLI version

Running Databricks CLI v0.294.0

Is this a regression?

Unknown