Dashboards performances - Timeouts & Errors

[JeanBlanc]

Hi everyone 👋

I'm currently troubleshooting a dashboard performance issue and I'm seeing a pattern I'd like to validate with the community.

When I select larger time ranges (e.g., 24h), some of the backend queries triggered by the dashboard are being aborted by the frontend — I consistently see net::ERR_ABORTED in the browser's dev tools.

🧪 Based on HAR analysis:

• The backend does not return an error.

• The request is cut off after ~450ms — even for valid queries.

• When I reduce the time range (e.g., to 30 minutes), the same queries complete successfully, even when they take longer (~580ms).

So my question is: Is there any known frontend-side timeout or cancellation mechanism that would abort requests if they take too long (e.g., >450ms)?

Any insights, docs, or similar experiences would be greatly appreciated!

Thanks in advance 🙏

[zietho]

Hey sorry for coming back rather late. Any news on your side? 
Is the this behavior still the same? 
Have you already raised a support ticket for this? 

[JeanBlanc]

Hey @zietho

The issue actually occurs when working with a large dataset.

In my case, I’m using a dashboard variable backed by an array of over 10,000 entries. The dropdown becomes very slow, and any query using an IN clause eventually times out.

I worked around it by changing the variable type to Text, which helped avoid the timeout. However, I lost the dropdown selection and autocompletion features in the process.

Do you have any alternative suggestions to handle such large datasets more efficiently?

Best regards,