Hi @Upendra_Dwivedi , are you still facing this issue?
The x-forwarded-access-token your app receives is the current user’s access token that Databricks forwards in HTTP headers for on‑behalf‑of‑user access. You should read it from the request on each call and pass it to downstream SDKs/connectors, rather than trying to have it persist.
You don’t need to redeploy the app when tokens change. Redeploys are only required when you enable/disable User authorization or change scopes; in those cases Databricks requires an app restart to apply the new authorization model.
How to fix
Do not cache the token or connection. Read x-forwarded-access-token per request and create a new DBSQL connection for that request; close it after executing the query. This avoids stale JWTs on connection reuse.
Use App authorization for long‑running/background work. For tasks that shouldn’t depend on a user session, call Databricks with the app’s service principal (OAuth client ID/secret injected as env vars), not the user’s token. This eliminates user-token expiry for those paths.
(see other resources/examples at github.com/databricks/app-templates and apps-cookbook.dev/)
If you have further questions please ask, but if this response helps you resolve the issue, then click the "Accept as Solution" button to let us know!
-James
