---
title: "Enable a custom failure reason"
method: POST
path: "/customFailureReason/{custom_failure_reason_id}/enable"
tags: ["CustomFailureReason"]
---

# Enable a custom failure reason

`POST /customFailureReason/{custom_failure_reason_id}/enable`

Re-enables a previously disabled custom failure reason. Requires Owner role. Cannot be used on default failure reasons.

## Path parameters

- `custom_failure_reason_id` string, required

## Response `200`

The enabled custom failure reason

- CustomFailureReason — A workspace-scoped failure reason used to categorize test run failures
  - `custom_failure_reason_id` string — Unique identifier for the custom failure reason
  - `workspace_id` string — The workspace this failure reason belongs to. Null for default failure reasons.
  - `display_name` string — The human-readable name displayed in the failure reason picker
  - `description` string — Optional short description of the failure reason
  - `agent_guidelines` string — Optional guidance prompt that helps result analysis decide when a failure should be assigned this reason.
  - `is_default` boolean — Whether this is one of the nine built-in default failure reasons
  - `disabled` boolean — Whether this failure reason is disabled. Disabled reasons are hidden from the picker but preserve historical assignments.
  - `created_by_id` string — The user who created this failure reason
  - `created_time` integer — Creation timestamp in epoch milliseconds
  - `last_updated_by_id` string — The user who last updated this failure reason
  - `last_updated_time` integer — Last update timestamp in epoch milliseconds

## Other responses

- `400` — Invalid or missing parameter
- `401` — User not authenticated
- `403` — User not authorized
- `404` — Entity not found
- `default` — Unknown error

---

[API](https://skmtc.net/mabl/apis/mabl-api.md) · [All operations](https://skmtc.net/mabl/apis/mabl-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mabl/mabl-api/revisions/d0fc0114da66/schema)