We have one account record (at least the only one that we have found thus far) that when a user goes to the skuid account detail page we have created, the Activity History table (Task) brings in completely unrelated records on page load. Then if you type in the search bar for the table, and then clear the search bar again, the filter conditions apply correctly.

This is the row count on the table from an un-related account at page load:

This is the row count on the table for the account discussed in the issue at page load:

And this is after typing in and then clearing the search bar:

The conditions on the Activity History table were designed to bring in Task records from all related account or contact records, whether through direct relationships or junction record relationships. The table is brought into the page via a page include component using another skuid page. This was done to isolate the models used for the Activity History because there are duplicate models of the same objects but with different conditions.