This is a known issue that has just been discovered. It will be fixed in patch 5.2.3 that should be out next week.
As a workaround you can include your whole script inside a Try container and use a "Go to the next iteration" action in the cache container.
Then configure your Try container to catch assertion error.
