-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[source-quickbooks] not working after access token expires #45911
Comments
Same issue here. It seems the mechanism to refresh the token is not working |
@pabloescoder are you working in other issue related to Quickbooks? Can you take a look into this one? |
@marcosmarxm I've made changes for the other issue and raised a PR, waiting for that to get merged because after those changes the refresh logic is working locally for me, there's an issue with the regression tests which is a blocker. Once that's resolved and that PR is merged, this should ideally be solved. |
Originally posted this here but I think I posed to the wrong thread, so adding it here for visibility. I have encountered this same issue using latest versions (Arbyte 1.3.0 + Quickbooks Connector 3.0.26) The initial sync works fine, however after 1 hour once the initial token expires, the sync fails with error: Steps taken to replicate the issue this morning:
![]() |
Hey @tomsweeting |
I am (extremely) proud to say this synced on it's own for me today in Cloud! Quickbooks finally works automatically! 🥳 |
Hey @pabloescoder thanks for the heads-up - that's exciting news! I will try upgrading to 4.0.0 tomorrow to test it out. |
@tomsweeting did you get it working? I'm still running an old version of the QB connector and it recently started failing. |
@chase-allenops I upgraded to QB connector 4.0.0 (and Airbyte 1.4.0) and the token refresh is working for me now. There is a caveat I have experienced though: It appears mid-sync auth token expiration is not handled gracefully, and will cause the sync to fail. When testing using the Airbyte internal scheduler set to hourly cron, I was seeing ~25% failure rate. Fortunately it does always recover on the next run with no manual intervention. I have not had any time to dig into why this happens, but I suspect it's not the fault of the QB connector itself since it uses that low-code API. In the final setup i'm using Airflow to trigger the sync, so putting a single retry works great and keeps the data on-schedule! |
@tomsweeting thanks for the in-depth response. Sounds like I need to bite the bullet and write my own QBO extractor. |
I was experiencing the 24 hours that was fixed by 4.0. As of March 12th, I am experiencing a similar error again. I can get the system to sync if I manually refresh the authentication token in the QBO developer playground and then put it into airbye each day. Below is the log from the error I get if I do not manually replace the authentication token. Appreciate any advice. 2025-03-14 10:35:45 info 2025-03-14 10:35:50 error Check failed |
Connector Name
source-quickbooks
Connector Version
3.0.3
What step the error happened?
Updating the connector
Relevant information
Added all OAuth 2.0 info
Setup the Token Expiry Date to be 1h after the access token was generated (or closer time to it in the :30 mins intervals it allows)
Initiated sync
Worked flawlessly until access token died (1h)
Received 401 error.
I tried both prod and sandbox, same error. I would appreciate your assistance a lot, thank you very much!
Relevant log output
Configuration check failed 'Unable to connect to stream accounts - 401 Client Error: Unauthorized for url: https://oauth.platform.intuit.com/oauth2/v1/tokens/bearer'
Contribute
The text was updated successfully, but these errors were encountered: