Analytics_tracking_error

💬 App Building
1

Hey folks,

I’ve been getting this recurring error in our logs for months now but cannot pinpoint where it is stemming from without access to the retool app source code.

ANALYTICS_TRACKING_ERROR

TypeError: Cannot read properties of undefined (reading 'sid')     at ncm (/retool_backend/bundle/main.js:311:444096)     at mn (/retool_backend/bundle/main.js:311:444485)     at Qoe (/retool_backend/bundle/main.js:331:3528)     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)     at async Timeout._onTimeout (/retool_backend/bundle/main.js:331:6336)

We’ve upgraded to self-hosted retool version 3.334-4.

I can’t find any mention of this error anywhere on the forums. Any help would be appreciated and if further information is required please let me know.

4

update: the only other mention of this error I have seen is in this thread

but their solution is to an unrelated issue.

@retool_team any suggestions?

5

Thanks for reaching out, @samthing! From everything that I see, this is just a noisy error that doesn't actually communicate anything of import. You can ignore it! That said, it's definitely noisy and we should probably handle the error more gracefully. I'll file a ticket internally. :+1:

1 Like
6

Thank you for the response! We have error monitoring setup and it is certainly making a lot of noise in our production logs. Is there an environment variable we can set that would suppress it?

7

I've done some additional research on this and don't think there's an easy toggle to suppress the error entirely. We can probably reduce the volume, though, by figuring out what is polling the relevant endpoints. Are you able to share logs that precede this error? The most likely explanation is a custom health check or uptime probe on your end.