> ## Documentation Index
> Fetch the complete documentation index at: https://developers.redo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# supportRuleOverlapWarningUpdate

> Dismiss a rule overlap warning or restore it, as the app's rules page does. A dismissed warning stays dismissed while the same rules overlap. Null, changing nothing, when no current warning of the store has the key.

**Required scopes:** [`support_rules_write`](https://developers.redo.com/docs/api-reference/v3/reference/scopes#scope-support_rules_write)

## Arguments

**dismissed** `Boolean!` *required*

**key** `String!` *required*

A warning's key, at most 2000 characters.

## Returns

**supportRuleOverlapWarningUpdate** `[SupportRuleOverlapWarning](/docs/api-reference/v3/reference/support/support-rule-overlap-warning)`

Two or more enabled rules on one trigger that change the same thing, as the app's rules page warns about them.

**fields**

**dismissed** `Boolean!` *required*

Whether the store dismissed it. The app lists dismissed warnings apart and leaves them out of its to-do count.

**key** `String!` *required*

Identifies the warning. It stays the same when rules are renamed or reordered, and changes when a different set of rules is involved.

**kind** `[SupportRuleOverlapKind!](/docs/api-reference/v3/reference/support/support-rule-overlap-kind)` *required*

**message** `String!` *required*

What happens, in English, as the app shows it.

**rules** `[\[SupportRuleOverlapRule!\]!](/docs/api-reference/v3/reference/support/support-rule-overlap-rule)` *required*

The rules involved, in run order.

**fields**

**defaultRuleKind** `[SupportDefaultRuleKind](/docs/api-reference/v3/reference/support/support-default-rule-kind)`

Which built-in rule this is. Null for a rule the store made.

**name** `String!` *required*

The rule's name: for a built-in rule, the name the app's rules list shows.

**severity** `[SupportRuleOverlapSeverity!](/docs/api-reference/v3/reference/support/support-rule-overlap-severity)` *required*

**suggestion** `String`

How to fix it, in English, when the app suggests one.

**target** `[SupportRuleOverlapTarget!](/docs/api-reference/v3/reference/support/support-rule-overlap-target)` *required*

**title** `String!` *required*

A short headline, in English, as the app shows it.

**trigger** `[SupportRuleTrigger](/docs/api-reference/v3/reference/support/support-rule-trigger)`

What makes the rules run. Null for a trigger that isn't on a ticket.

## Errors

Besides the [errors any request can return](https://developers.redo.com/docs/api-reference/v3/errors.md), this operation fails with these codes in `extensions.code`.

| Code | HTTP status | Meaning | Retry |
| - | - | - | - |
| `API_TOKEN_REQUIRED` | `403` | The credential has no API token to attribute the change to, such as a first-party token. Nothing was sent. | Call with a store API token. |
| `BAD_USER_INPUT` | `400` | An argument is invalid, or names something the store doesn't have. The message says which. Nothing was written. | Fix the input the message names, then send it again. |
| `INTERNAL_SERVER_ERROR` | `500` | Something failed on Redo's side. The change may or may not have been made. | Read the record to see whether the change was made before sending it again. A send with an idempotencyKey is safe to retry with the same key. |

## Example

```graphql theme={null}
mutation {
  supportRuleOverlapWarningUpdate(dismissed: true, key: "...") {
    dismissed
    key
    kind
    message
    severity
    suggestion
    target
    title
    # ...
  }
}
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.