In general during the same interaction you cannot 100% guarantee that something written to the database can be immediately queried from the database. Suppose Container Managed Transactions (CMT) is used where saves are handled outside of Pega by the App Server. The same applies to saving data then immediately expecting a read-only List Data Page to display the record in its list.
Perhaps a Standard Agent (7.X) or Queue Processor (8.X) can be used. Queue-based agents restore the step page, which must have been committed, then pick up where you left off on your behalf.
The agent will retry as long as the cover is locked.