The QB Online token refresh process is periodically failing and then resulting in portal accounts losing the QB Online connection. The current process takes place in real-time as requests are made. This process can fail once or twice before "giving up", at which time the active token can't be refreshed. It's not fully apparent why the failures occur as we are seeing a somewhat generic error being logged.
The current plan is to rewrite the refresh process to take place in the background rather than in real-time. The idea is that we can allow retries to happen over a much longer span of time in the event that their is a failure with the refresh. QB Online API tokens have a one hour TTL, so we will likely begin to refresh any token that has reached 40-45 minutes in age. That gives our servers 10-15 minutes to retry and fetch a refreshed token before the current token expires.
The QB Online token refresh process is periodically failing and then resulting in portal accounts losing the QB Online connection. The current process takes place in real-time as requests are made. This process can fail once or twice before "giving up", at which time the active token can't be refreshed. It's not fully apparent why the failures occur as we are seeing a somewhat generic error being logged.
The current plan is to rewrite the refresh process to take place in the background rather than in real-time. The idea is that we can allow retries to happen over a much longer span of time in the event that their is a failure with the refresh. QB Online API tokens have a one hour TTL, so we will likely begin to refresh any token that has reached 40-45 minutes in age. That gives our servers 10-15 minutes to retry and fetch a refreshed token before the current token expires.
gtmadev
added this to the GoToMyAccounts project 2025-10-27 07:56:43 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The QB Online token refresh process is periodically failing and then resulting in portal accounts losing the QB Online connection. The current process takes place in real-time as requests are made. This process can fail once or twice before "giving up", at which time the active token can't be refreshed. It's not fully apparent why the failures occur as we are seeing a somewhat generic error being logged.
The current plan is to rewrite the refresh process to take place in the background rather than in real-time. The idea is that we can allow retries to happen over a much longer span of time in the event that their is a failure with the refresh. QB Online API tokens have a one hour TTL, so we will likely begin to refresh any token that has reached 40-45 minutes in age. That gives our servers 10-15 minutes to retry and fetch a refreshed token before the current token expires.