We have a view with a tab container that has a table of a summary on the first tab and several other tabs that each have flex repeaters.
The summary and flex repeaters (share same binding) gets it's data each from a custom property with a named query binding. With the two bindings, each returns about 35 rows by 45 columns, nothing too bad.
However, sometimes, several times per hour, only partial results come back, where the table will only show 6-8 rows and the flex repeater will be blank. One can simple navigate out and back in to refresh to get the full results, but this happens often enough to cause an inconvenience to the end users.
This view and database is designed to run by live updates, so once something is entered, it updates the db and refreshes the binding, thus named query. We would like to keep it that way. The database does have indexing and such to make the queries usually 200-300ms each, but once in a while get a 1-3 second query. I don't think I want to cache the name query due to the instant live update design.
Is there any other recommendations on what I can do to improve this?