Forum Discussion
Access token has expired
definitely continue with the support team to inquire more about the refresh of your credentials. If you are effectively using username/password (aka basic auth), then there isn't anything to refresh in terms of tokens, because the basic authentication never needs any sort of refresh. It simply uses the same username/password.
However, if you are leveraging a destination such as a LakeHouse or a staging mechanism, then the tokens for those could potentially expire while the refresh is happening.
Hey Jim,
As you've mentioned, if you are using a gateway then there are some limitations / considerations associated with it when it comes to online sources that have expiring tokens. You can read more from the link below:
Data Factory limitations overview - Microsoft Fabric | Microsoft Learn
There isn't a workaround, but the team is actively working to address this, but its definitely a good idea to raise a support ticket as that sort of signal helps us identify how many users are being impacted (and how impactful it can be) by this limitation.
Hi miguel,
We tried ingesting the table in its entirety with both Vnet and onprem gateway, with unsuccessful outcomes. With the onprem gateway, a ticket was filed and the recommendation is to create a multinode cluster. While we don't rule that out, the Vnet is preferred because it's less maintenance. We don't use OAuth with the Vnet, which is why we wonder the creds expire; we know expiration happens, but we were hoping that with basic auth, it would last longer.
definitely continue with the support team to inquire more about the refresh of your credentials. If you are effectively using username/password (aka basic auth), then there isn't anything to refresh in terms of tokens, because the basic authentication never needs any sort of refresh. It simply uses the same username/password.
However, if you are leveraging a destination such as a LakeHouse or a staging mechanism, then the tokens for those could potentially expire while the refresh is happening.
miguel Thanks much for the feedback. We are running with staging disabled but we are using a lakehouse as the destination. So, just to make sure that I understand correctly, the error I am experiencing could be coming from the token used for connecting to the lakehouse and it's a built-in limitation?
It could be. It really depends on how long your refresh is running. The logs of the gateway could you give you more information to see if thats the case and if the token just expired and thats why you can't connect to the Lakehouse. It could also be something else, but its a good idea to have the support team help you review those logs.