Help for owners
My app keeps losing its connection to QuickBooks and asks me to log in again
Short answer
A QuickBooks link that keeps dropping usually means the app cannot keep its stored permission up to date: two copies of it are fighting over one login, the person who connected it changed, or it stores the renewed permission badly. Reconnecting only resets the clock. Note when each drop happens and send that to your developer.
Does this sound like your situation?
- Every few weeks the app says the QuickBooks connection has expired and I have to authorise again.
- It disconnects at odd times, even though nobody changed anything.
- I reconnect, it works for a while and then drops again.
- A test version and the live version of the same tool both use my QuickBooks company.
- The person who first connected it has left or changed their login.
Why does this happen?
Two copies are using one connection
When a test site, a second server or an old version of an integration all hold the same stored permission and each tries to renew it, one renewal can invalidate the copy held by the others. The one that loses the race starts failing and shows a disconnect. A connection that only breaks after a deployment or a new server usually points here.
The renewed permission is not saved
Connections of this type work by exchanging a stored token that the app has to renew and save again. If the save step fails, or the app saves it to a place that is wiped on restart, the app is left holding an old one, and the next renewal fails.
Technical detail: The token endpoint answers with unsupported_grant_type
Nobody used it for a long stretch
A connection that sits idle, for example a seasonal tool or a paused job, can lose its permission. The cure for the owner is the same each time, which hides that the app never renews it on a schedule.
The person who connected it changed
The connection acts as that user. If the account is deleted, its role is reduced, or someone removes the app on the QuickBooks side, the link ends.
The app handles the failure badly
A good integration notices a failed renewal, stops sending, tells you, and waits. A poor one keeps retrying, so a normal expiry looks like repeated disconnects and half-sent data.
What can I do about it today?
- Write down each dropDate, time and what happened just before: a deployment, a password change, a new user, a long quiet period. The pattern points to the cause.
- Check who connected itIn QuickBooks, look at the list of connected apps and who authorised them. Confirm that person is still active with an appropriate role.
- Ask whether more than one version is runningA test copy, a staging site or a second server using your live QuickBooks company is the most common hidden cause. Ask your developer or host to list them.
- Reconnect once, at a quiet time, only after the aboveReconnecting repeatedly while a second copy is running can make it worse. Do it once and tell your developer the time.
- Send the notes to your developerThe dates, the screenshot of the connected apps page and who authorised the link.
When should I bring someone in?
- The drops are frequent and money data, such as sales or payments, is not arriving in between.
- Nobody knows who connected the link or where the tool stores its login.
- A reconnect works for a short time and then fails again.
How do I handle it?
- Find every place the connection is usedI read the vendor's current documentation first, and every change is tried on test data before it touches your real books. I list each copy of the integration, live, test and old, and which stored login each one holds.
- Fix how the login is stored and renewedThe renewed permission is saved in one safe place with a single renewal path, so two processes cannot overwrite each other.
- Separate test from liveTest copies are pointed at a separate test company, so they cannot use your real books.
- Make failure visibleA failed renewal pauses the sync and sends you a message, and sending resumes in order after the link is restored.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is a regular reconnect just normal?
A well-built integration renews its permission by itself and does not need you. If you are being asked to log in again often, the integration is the problem, not you.
Could QuickBooks be blocking my app?
It is possible but less common than a handling problem inside the app. Check the connected apps page and your developer's logs before assuming the provider changed something.
Will I lose data when it disconnects?
Data already in QuickBooks stays. What can be lost is anything the app tried to send while disconnected and never retried, so ask for a count check after you reconnect.
How was this page made?
I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.