The "CPM failed: Too many cycles: Max 5 cycles exceeded" error will be added to the error and info logs on a site interface when there is a problem with API suppression involving a synchronous CPM. This is an indication that the CPM has entered a loop, and the error can be resolved by ensuring the site implements API suppression appropriately, as described here:

 

 

You will not see this error with CPMs that are configured to run asynchronously, however, as looping with them will result in new CPM records added to the queue instead (of the condition that causes the "Too many cycles error"). This will often result in a delayed/backed up queue, and for details on this condition see