Hi,
I'm experiencing a preview issue on Retool, even with the latest server version (3.148.5). The queries seem to be running late—we're pulling data from the Datadog API v1, but I can't see the results when I try to preview them. Additionally, the app isn't saving properly and shows a "Failed to save" error.
Do you guys have any ideas or suggestions on how to resolve this?
Thanks,
Welcome to the community, @anldrms! Thanks for reaching out. 
To start, the Failed to save error is fairly generic but can most often be attributed to having multiple editor sessions open, whether across multiple tabs or machines. Let us know if you continue to notice any odd behavior!
Based on the screenshot that you've shared, it looks like your query is running and returning data just fine. Your table, however, may need some additional configuration - specifically, it looks like no columns have been defined. You should be able to open up the component inspector and choose the option to Generate columns from data source.
I hope that helps! Don't hesitate to follow up here if you have any additional questions. 
The data is loading correctly, but I noticed something interesting — when I reduce the filter count to just 1, the data becomes visible in the table. This makes me wonder if the issue could be related to a server-side limitation or performance bottleneck when handling larger result sets. Could this be a server-side issue?
Ah I think I might have missed an important nuance. Are you only seeing this issue when previewing the app? And just to narrow down its scope, can you confirm that the backing query executes and returns the expected data?
To your question, it doesn't sound like a server-side issue - at least not one that I've seen before. If I'm correctly understanding the above, it still sounds like the root of the issue lies in the filtering that you're doing or the way the table component is configured. Are you able to share screenshots or even a JSON export of your app?
Let me know if this is still an issue for you, @anldrms! If it is, any additional context would be super helpful towards identifying the root of the issue.
