Skip to main content
R
RTUK
April 7, 2022
Solved

Quickbooks Online: Lag When Saving New Customers, Projects or Items

  • April 7, 2022
  • 1 reply
  • 0 views

After using Quickbooks Online (QBO) for a while, we have noticed that every time we add a new Customer, Project or Item there is a delay between creating it and being able to use it on a transaction. Sometimes this can be up to 30 minutes.

 

We fully understand that QBO is a SAAS application and probably uses some kind of database replication where information is written to a central master database and the slave databases need to catch up (replication lag).

 

This lag can be up to 30 minutes.

 

Assuming QBO is indeed using database replication, has this delay/lag been identified as an issue and is it in hand? If not, where is the QBO bug tracker so that we can raise this?

 

Best answer by GeorgiaC

Hi RTUK, thanks for your post. Once saved, the new contact or item should be instantly available to use - we recommend in the first instance checking for any cache issue which may be causing a delay on your browser. You can do this by following the steps on our guide linked here; additionally, it's good to check that the system you're using meets the system requirements and minimum operating speeds. If you're still finding that performance is slow after checking these, please see our tips to improve speed to eliminate lag and get the best experience possible 👩‍💻

1 reply

G
GeorgiaCAnswer
April 7, 2022

Hi RTUK, thanks for your post. Once saved, the new contact or item should be instantly available to use - we recommend in the first instance checking for any cache issue which may be causing a delay on your browser. You can do this by following the steps on our guide linked here; additionally, it's good to check that the system you're using meets the system requirements and minimum operating speeds. If you're still finding that performance is slow after checking these, please see our tips to improve speed to eliminate lag and get the best experience possible 👩‍💻

R
RTUKAuthor
April 7, 2022

We have accepted this as the solution because it did solve the issue.

 

However, it's important to note that if this is not replication lag and an issue with caching ajax requests. The request needs to check for changes.

Terms & ConditionsAccessibility statement