Issue Summary

Currently, if an action fails, there is little recourse for addressing the problem.

For example, for the outbound webhook action, there is a checkbox for "
Continue running the rule even if the request response is not successful (i.e. non-200 response)", however, there is no ability to reattempt (may be a transient issue for 429), or to report an error.

Suggestion

A retry may be valid for a case of 429. The use case needs to be considered carefully - a single or very small number of reattempts may be useful. Significant complexity may be introduced if attempting to implement exponential backoff based on the response.

In the case of a 5xx error, it may be useful for the rule to leave a comment - "unable to trigger build" so that a non rule administrator may deal with the problem:

if not 2xx:
    leave comment

implying:

if not 2xx:
    leave comment
else:
    continue with other actions