Github user joewitt commented on the issue: https://github.com/apache/nifi/pull/3078 We should avoid calling this processor a 'PenalizeFlowFile' processor. First, we have a notion of penalization in the framework already and it has a very specific meaning and it kicks in when processors reach certain failure conditions that are believed to be specific to a given flowfile or set of flowfiles and that by penalizing them the condition might improve on its own. Second, the use for this processor in a flow might not be for the purposes of penalizing that flowfile but rather might simply be to cause a given wait or hold to occur. I'd recommend calling it DelayFlowFile. <...then I went and looked at the code> It is literally just calling penalize flow file so it makes sense why the name was given. What use case is this for again? If we're really wanting to create a DelayFlowFile processor, which is what it sounds like was the intent, we should do that because penalization means something else.
---