Latency between Matching API Cron Jobs

Hi Omar,
Currently Matching API is a batch process that's run when Cron is run to build another

table with all the matches, right? If so, then for frequently updated information there's

inherent latency between when the data is entered and when it's available in the Match

table just like Drupals Search Indexes, right?

If so, is there a way to fill the gap? Using a table for performance is great but

providing users with the latest information to be available is also critical in some

situations.
Regards.