Redis Node: Error 'no such key' when attempting to create a list with set request

[ARHAEEM]

Bug Description

When using the Redis node in n8n to create a list with the set request, I encounter the following error:

{
  "errorMessage": "ERR no such key",
  "errorDetails": {},
  "n8nDetails": {
    "n8nVersion": "1.58.0 (Self Hosted)",
    "binaryDataMode": "default"
  }
}

The key does not exist, but unlike strings and sets, it should create the key if it doesn't already exist. Instead, it throws an error for lists. The expected behavior is for Redis to create the key automatically when setting a value for the first time.

To Reproduce

Steps to reproduce the behavior:

1. Set up an n8n workflow with a Redis node.
2. Use the set request for a list key that does not exist.
3. Observe the error message ERR no such key.

Expected behavior

The Redis node should create the list key if it does not exist, similar to how it works with strings and sets. There should be no error, and the key should be created when setting a list.

Operating System

Ubuntu Linux 22.4

n8n Version

1.58.0 (Self Hosted)

Node.js Version

Default Docker image.

Database

PostgreSQL

Execution mode

main (default)

[Joffcom]

Hey @ARHAEEM,

We have created an internal ticket to look into this which we will be tracking as "GHC-218"