Missing or Delayed Data
Sometimes data doesn’t reach devgrowthlab as expected. Most of the time, this happens because of network interruptions, connectivity issues on mobile devices, or request rate limits.
Under normal conditions, data ingestion takes about half a second for users on reliable connections such as Wi-Fi. On mobile networks, where conditions vary, it’s a good idea to set a network timeout of about thirty seconds to give requests time to complete. If a request fails or the network can’t be reached, you can safely resend the data later. When doing this, include the original timestamp in the nowSeen field. This value can be either milliseconds or seconds since the Unix epoch, whichever suits your environment. The timestamp helps devgrowthlab understand when the event actually occurred, especially if the resend happens the next day.
Each device is limited to one request per second. If you need to retry a failed submission, wait at least a second between attempts and ideally double the wait each time a retry fails. This backoff approach prevents accidental overloading and helps the service stay responsive for everyone.
If you receive a 403 error, don’t attempt to resend the data. That status means the ingestion key is no longer valid - for example, it might have been removed after you cancelled a plan. Continuing to resend after that makes it harder for us to maintain the low cost of the service.
Data in the dashboard is displayed in UTC and updates only once daily. You won’t see today’s partial data until the following day’s update. Data sent around midnight UTC might appear in the next day’s results, so it’s best to keep that in mind when reviewing graphs.
If you suspect a larger issue, such as repeated failures or delays across multiple users, contact support. While we can’t debug individual submissions, we can investigate systemic issues that you can reliably reproduce. In some cases, our team may ask for a small code example that demonstrates the behaviour so we can help you find the cause quickly.