Overview
Sometimes a Databricks access token is extended, but the updated expiration date does not appear in Amperity. This can make it look like the token is still expiring soon, even though it has already been extended in Databricks.
This article explains why this happens and how to fix it.
Why This Happens
When you extend or update a Databricks token directly in Databricks, Amperity does not automatically pick up that change.
Amperity only refreshes the token details when the credential is re-uploaded through the Databricks inbound share settings. Simply extending the expiration date in Databricks does not push the update into Amperity.
Because of this:
Databricks shows the new expiration date
Amperity continues to show the old expiration date
Solution: Re-Upload the Credential in Amperity
To reflect the updated token expiration in Amperity, you must re-upload the credential for the Databricks inbound share.
Steps
Go to Sources in Amperity
Open the Databricks inbound share
Click the three-dot (⋯) menu next to the inbound share
Select Upload credential
Upload the token that has the updated expiration
Save the changes
Once this is done, the new expiration date will appear correctly in Amperity.
Expected Result
Amperity shows the updated token expiration date
No credential expiry warnings
Inbound share continues running without interruption
Important Notes
Extending a token in Databricks alone is not sufficient
Amperity does not auto-sync token expiry changes
Re-uploading the credential is required after:
Token extension
Token renewal
Token rotation
Summary
Token expiry changes made in Databricks do not automatically update in Amperity
The credential must be re-uploaded in Amperity using Upload credential
Once re-uploaded, the correct expiration date is reflected and the issue is resolved