Data that is created/modified in dataverse from an another interface is not pushed in real time to the Portal Cache. The primary record that is created/updated from the Portal is available in real-time - secondary records (e.g. a plugin that triggers on create of the primary record that creates a related record) are not pushed to the cache in real-time.
the SLA for the push to the cache is 15 mins but usually occurs within a couple of minutes.
The only way to surface such records is to break the cache (by including conditions on the query that will make the query have to go to dataverse and not the cache e.g. include createdon equals now down to seconds) which can be done if making the queries yourself and not using the standard Lists etc. = breaking the cache is not recommended
Also, this is by design by Microsoft - in the old days it was more real-time and in the old old days you could push the data from dataverse,
