## TL;DR

On Redis Cloud the maxmemory ceiling is the database's size limit, so you cannot just CONFIG SET a bigger one. Either enable an eviction policy (allkeys-lru on a cache, volatile-lru when only some keys have TTLs) so writes stop failing, or resize the database to a larger size in the Redis Cloud console. Monitor with INFO memory and alert on used_memory over 80 percent of the limit so the next fill-up is planned, not discovered.

## Fix

1. On Redis Cloud the maxmemory ceiling is the database's size limit, so you cannot just CONFIG SET a bigger one.
   Expected: You get the expected result; the problem is gone.
2. Either enable an eviction policy (allkeys-lru on a cache, volatile-lru when only some keys have TTLs) so writes stop failing, or resize the database to a larger size in the Redis Cloud console.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are setting up or using this Redis Cloud feature.
- The symptom matches: OOM command not allowed when used memory > maxmemory.

## When NOT to use

- Unrelated Redis Cloud issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Redis Cloud. Source: https://github.com/plug1210/automationhelper_plugins/blob/HEAD/Docs/N8NDocs/Database/redis.md.

## Variant phrasings

### OOM command not allowed when used memory > maxmemory

## Why it happens

Writes to a Redis Cloud database fail with OOM command not allowed when used memory > 'maxmemory'. The database has hit its storage limit.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.

## Source

https://github.com/plug1210/automationhelper_plugins/blob/HEAD/Docs/N8NDocs/Database/redis.md