Omar Ajoue

Thanks @jburgers-chakray for your PR. I've made a few fixes and tiny adjustments and created another PR. Closing this one in favor of https://github.com/n8n-io/n8n/pull/8588

I was testing this and found 2 issues:  First one is this, where there's apparently a console log message. ![Screenshot 2024-03-12 at 16 49...

@ersinors I was having a look at this issue and could not find any exact details in the docs, but I couldn't find any strong evidence that AWS Serverless Redis...

Just to give more context on my previous comment, from https://repost.aws/questions/QUDyEltSQJTsOu22rfUbhd5A/connect-to-elasticache-serverless-using-nodejs-ioredis it seems to use a regular `new Redis` instead of `new Redis.Cluster`. Under the hood, this is exactly what...

Thanks for the additional context @aeb-dev I tried investigating this but unfortunately my knowledge about AWS Elasticache for Redis Serverless is limited. I spent some time setting it up but...

I'll be closing this issue for now as n8n is working with regular Redis and this is our requirement to run queue mode. Since Redis is still well and kicking...

@netroy changed the way we reported the error, instead of using the message, to use the proper metadata attribute. WDYT?

Had the issue with `/usr/bin/env: node -r esm: No such file or directory` and had it solved using `node -r esm ./bin/server` but now I'm getting this error with node...

I took a good look at the file and it seems ok. I used JSON validators and JSON lint, it's all right. The position mentioned (1492) in the error is...

btw we'll probably have to update this before merging the feature branch once job's over