Failed Actions Tracking and Retry System

the failed actions tracking system gives you visibility and control over actions that fail during content moderation when nima applies an action to reported content, the webhook carrying that decision to your platform can fail — your endpoint may be unavailable, or return an error this feature helps you identify, track and resolve those failures visual indicators failed actions are colour coded in the reports list orange automatic retries are still in progress — the 9 attempts have not yet been exhausted red all 9 attempts have been made and none succeeded if you read case status over the api rather than the interface, the same information appears as 1 fails through 9 fails , incremented with each attempt filtering failed cases a dedicated filter option allows you to quickly identify all failed actions in the reports list, set the status filter to failed reports the appeal list offers the equivalent option this shows only items with failed webhook actions, both orange and red viewing failed action details when you open a case or appeal marked orange or red, select action failure details at the bottom of the right hand panel it opens a drawer with everything nima recorded about the failure action id unique identifier for the action response code the http status code received from the endpoint response body the complete response returned from the endpoint attempts how many attempts have been made so far executed on the date of the most recent attempt automated retry mechanism nima makes up to 9 delivery attempts in total — the initial attempt plus 8 automatic retries the process follows these steps the initial delivery attempt fails the case is marked orange in the reports list nima retries automatically, up to 8 further times if any attempt succeeds, the case status becomes processed if all 9 attempts fail, the case is marked red in the reports list manual retry becomes available webhook deliveries run on their own dedicated queue, isolated from the rest of nima's processing an endpoint that is down and being retried does not slow down moderation elsewhere on your instance if a delivery succeeds and your response body contains an evidence url , nima stores it against the content — provided the content does not already have one manual retry functionality once a case is marked red, you can retry the action by hand the retry action button is visible before then but stays disabled, with a note explaining that it becomes available once the automatic attempts are exhausted open the case review the failure information in the drawer select retry action nima runs the same delivery workflow again, with the same allowance of up to 9 attempts if it succeeds the case status updates accordingly; if not, the case returns to red everything described here — the colour coding, the filter, the failure drawer and manual retry — works the same way for appeals as it does for cases