Reprocessing a request means running it again through the platform’s current rule framework so it is evaluated with the latest rule configuration.

This is useful if a rule has been created or adjusted after the request was first made and you want the request evaluated retroactively against the new conditions. It can also be used if an error ping occurred due to a temporary downtime from a data provider, or if required data was missing the first time, preventing the rule from running successfully.

When reprocessing a request, any potential error ping is automatically ignored, all other pings stays untouched. Also, Cases must still be handled manually.