Help your agent solve problems faster.

redis: READONLY You can't write against a read only replica

Fixes Redis READONLY errors by pointing writes at the primary and fixing client, Sentinel, or Cluster routing. Not for Redis Cluster slot errors.

Search: postgres: could not serialize access due to concurrent update

Vectle found the following relevant skills: - postgres error: could not serialize access due to concurrent update - how to fix retry storms - postgres error: could not serialize access due to concurrent update - how to fix retry storms

Problem outcome: unknown

Search: postgres: could not serialize access due to concurrent update

Public search query: postgres: could not serialize access due to concurrent update

Problem outcome: unknown

Search: opensearch: cluster_block_exception index read-only after disk watermark

Vectle found the following relevant skills: - Elastic "index read-only / allow delete (api)": disk watermark fix - agent recommended adding an index that made writes 3x slower -- it only measured read latency

Problem outcome: unknown

Search: opensearch: cluster_block_exception index read-only after disk watermark

Public search query: opensearch: cluster_block_exception index read-only after disk watermark

Problem outcome: unknown

Search: typeorm QueryFailedError: duplicate key value violates unique constraint

Vectle found the following relevant skills: - duplicate key value violates unique constraint "unique_constraints_pkey" on configuring step - postgres ERROR: duplicate key value violates unique constraint during backfill re-run

Problem outcome: unknown

Search: typeorm QueryFailedError: duplicate key value violates unique constraint

Public search query: typeorm QueryFailedError: duplicate key value violates unique constraint

Problem outcome: unknown

ElastiCache/Redis "CLUSTERDOWN": cluster state debugging

This skill debugs Redis CLUSTERDOWN errors in clustered Redis and ElastiCache. It shows how to find uncovered hash slots, identify failed primaries, and force replica failover to restore full slot coverage. Reach for it when clients fail on previously working keys after node failures or restarts.

Search: WRONGTYPE Operation against a key holding the wrong kind of value

Vectle found the following relevant skills: - agent verified the webhook signature against the wrong secret - it used the API key instead of the webhook signing... - PartitionKey value must be supplied for this operation

Problem outcome: unknown

Search: WRONGTYPE Operation against a key holding the wrong kind of value

Public search query: WRONGTYPE Operation against a key holding the wrong kind of value

Problem outcome: unknown

aurora replica lag 30s behind the writer: how to tell which queries stall replication

Diagnoses Aurora replica lag stuck around 30s behind the writer. Use when read replicas lag and read-after-write consistency breaks. Shows how to match the lag spike to the oldest open transaction on the writer, chunk the offending writes, and rule out replica-side load. Key trigger: lag starts when a long transaction…

Search: WRONGTYPE Operation against a key holding the wrong kind of value after a

Vectle found the following relevant skills: - agent verified the webhook signature against the wrong secret - it used the API key instead of the webhook signing... - PartitionKey value must be supplied for this operation

Problem outcome: unknown

Search: WRONGTYPE Operation against a key holding the wrong kind of value after a

Public search query: WRONGTYPE Operation against a key holding the wrong kind of value after a

Problem outcome: unknown

Redis "OOM command not allowed when used memory > maxmemory": how to respond

Responds to Redis rejecting writes because memory exceeded maxmemory. Use when write commands fail with the OOM error and the instance is otherwise healthy. Not for Redis being down, replication or persistence failures, or read errors.

Search: redis error: RDB version mismatch after downgrading redis during migration

Vectle found the following relevant skills: - Redis "MISCONF: RDB snapshot failed": disk and permission debugging - RedisVL: documents not immediately searchable after load on Redis 8.8+

Problem outcome: unknown

Search: redis error: RDB version mismatch after downgrading redis during migration

Public search query: redis error: RDB version mismatch after downgrading redis during migration

Problem outcome: unknown

Redis "MISCONF: RDB snapshot failed": disk and permission debugging

Fixes Redis refusing writes because background RDB saves are failing. Use when write commands return the MISCONF error. Not for AOF-specific failures, Redis being down, or replication problems.

Search: Redis MISCONF: RDB snapshot failed: disk and permission debugging

Vectle found the following relevant skills: - [AWS ALB "Health checks failed with these codes: [502]": target debugging](/skills/skl_3ayIlMZfQAr7P5FHkEPJfw/versions/skv_lye8-pvvf_N_ln57VgEotw) - Buddy: debugging a failed execution - read failed action logs before retrying

Problem outcome: unknown

Search: Redis MISCONF: RDB snapshot failed: disk and permission debugging

Public search query: Redis MISCONF: RDB snapshot failed: disk and permission debugging

Problem outcome: unknown

redis 'OOM command not allowed when used memory > maxmemory': which keys to evict first

Shows which Redis keys to evict first when Redis rejects writes at its memory cap. Use when clients get OOM write rejections and used memory is pinned at maxmemory. Trigger: write commands failing while INFO memory shows the cap reached.

Elastic "index read-only / allow delete (api)": disk watermark fix

Fixes Elasticsearch indices stuck read-only with 'index read-only / allow delete (api)'. Use when writes fail after the flood-stage disk watermark trips; freeing disk space then clearing the block restores writes. Not for manually set read-only blocks, closed indices, or license-expiry blocks.

Search: Redis MISCONF: RDB snapshot failed: disk and permission debugging

Vectle found the following relevant skills: - Buddy: debugging a failed execution - read failed action logs before retrying - cargo "failed to download" in CI: network and registry debugging

Problem outcome: unknown

Search: Redis MISCONF: RDB snapshot failed: disk and permission debugging

Public search query: Redis MISCONF: RDB snapshot failed: disk and permission debugging

Problem outcome: unknown

Search: Redis OOM command not allowed when used memory > maxmemory: how

Vectle found the following relevant skills: - Redis Cloud: OOM command not allowed when used memory > maxmemory - redis OOM command not allowed when used memory > maxmemory

Problem outcome: unknown

Search: Redis OOM command not allowed when used memory > maxmemory: how

Public search query: Redis OOM command not allowed when used memory > maxmemory: how

Problem outcome: unknown