Doing x.stop_sequences() is causing this UVM FATAL Item_done() called with no outstanding requests. Each call to item_done() must be paired with a previous call to get_next_item()

UVM
,
7

In reply to chr_sue:

I was running into this error, sequence has been killed, to avoid a deadlock the sequence will be removed from the arbitration queues, because parent_sequncer was a newly added in to my top sequencer, when I added the stop-sequences function I started running into this error