Thanks for your response.
But I'm observing a situation as below suppose there are couple of preprocessing rules situation you might have encountered this as well:
Scenario-1
1-is an exclude rule
2-is custom where a script is executed
In this case the ouput of exclude is used by custom as feed. This enters into a loop as output of custom again is consumed by exclude as feed.
Scenario 2
1-is a custom where a script is enriching the source
2-is custom where a script is executed
In this case 2 does not trigger, 2 is only manipulating severity, and skips any output coming from 1.
I believe if ordering was available this could have been handled a lot easier
Though I've figured out a workaround as well but again I don't see the purpose of omitting ordering under preprocessing.