Is there a delay between a resumable user getting suspended and the "after suspend" trigger being fi

Oracle 12.1.0.2

The alert log started to report "ORA-1691: unable to extend" at 10:49, and continued to do so.  The first thing we have in our "after suspend on database" trigger is to write a message to a log table.  The first message in the log table was at 10:59, after which our set up resolved room problem by 11:00.  So why did it take 10 minutes for the "after suspend on database" trigger to fire?  That's a long time to waste.  I did not see this happen on 11.2.0.3 or 10.2.0.4.  Is there something new in 12.1.0.2 that puts a delay