In reply to cgales:
The reset is applied in the application code. Specifically, I have my own routine that just triggers the system reset line for some number of cycles. When this is applied, the sequencer/driver has been quiet for perhaps over a thousand clocks, so it’s not a problem with resetting during a transaction. The last transaction has certainly finished normally before the long wait then reset cycle.
I’m more interested in some ways that I can debug into the UVM library to find clues as to why get_next_item is stalling for me.