# ERR ACL categories 'write' and 'readonly' cannot be combined for user 'myuser'

- **ID:** `redis/acl-category-inheritance-conflict`
- **Domain:** redis
- **Category:** config_error
- **Verification:** ai_generated
- **Fix Rate:** 95%

## Root Cause

User configuration contains conflicting ACL category permissions; 'write' allows write commands while 'readonly' restricts to read-only, causing an invalid state.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| Redis 7.0.0 | active | — | — |
| Redis 7.2.0 | active | — | — |
| Redis 7.4.0 | active | — | — |

## Workarounds

1. **Remove the conflicting category using ACL SETUSER myuser -readonly (or -write) to ensure only one set of permissions is active.** (95% success)
   ```
   Remove the conflicting category using ACL SETUSER myuser -readonly (or -write) to ensure only one set of permissions is active.
   ```
2. **Recreate the user with a single category: ACL SETUSER myuser on >password +@readonly ~* to grant read-only access without write permissions.** (90% success)
   ```
   Recreate the user with a single category: ACL SETUSER myuser on >password +@readonly ~* to grant read-only access without write permissions.
   ```
3. **Audit the ACL rules file (e.g., users.acl) and manually edit to remove the conflicting line, then reload with ACL LOAD.** (85% success)
   ```
   Audit the ACL rules file (e.g., users.acl) and manually edit to remove the conflicting line, then reload with ACL LOAD.
   ```

## Dead Ends

- **** — Adding more conflicting categories (e.g., both 'admin' and 'restricted') only exacerbates the conflict without resolving it. (90% fail)
- **** — Deleting the user and recreating with the same conflicting categories will reproduce the same error. (95% fail)
- **** — Ignoring the error and proceeding with other operations may leave the user in an inconsistent state, causing unpredictable behavior. (70% fail)