Hello All,


I currently have a duration limit set while running expiration.  Occasionally
while the processes is running the limit is ignored or not rezognized and
expiration continues over the assigned specified time limit (currently set for 4
hours and the last expiration process ran for 9 hours).

This causes migration processes that are scheduled after the expiration is
scheduled to finish to fail with lock failures.

Has anyone else experienced this problems

Thanks