Sometimes (but really just sometimes, not always) builds have very high numbers of build triggers, if the "retrigger on node interruption" option is enabled for a cloud. Generally that does not affect the build result, but just adds some more lines like this to the console:

However, we've meanwhile seen cases where the numbers are high enough to create critical log sizes, like this build with 32 GB log size just because of the triggers:

I'm not sure how exactly the "retrigger on interruption" option is implemented, but it certainly needs some kind of internal delay or back-off, to avoid firing many, many times repeatedly for the same single node interruption.