Lock a sequencer from virtual sequence

In reply to adityaprasad123:

Without a running representative testcase, it is difficult to isolate the issue. The lock() call waits until the sequence is arbitrated, so it’s possible that other sequences are being run which competes with this sequence.

Have you tried using grab()/ungrab()? This will preempt the arbitration and take immediate control of the sequencer.