Records deleted in an autonomous transaction within stored procedure still available later inside the procedure

[malpacasville]

I have a stored procedure that deletes some expired data using "in autonomous transaction do", it does this so the delete isn't rolled back if the procedure throws an exception later. I am finding the data still exists for statements outside the autonomous transaction later in the procedure. (I'm using db.execute with pooling).

I could rework how this particular function works to get around it, but I don't know where else in our system it might cause issues.
The procedure works fine when calling it from SQL manager or a different API connection to the database.