[BullMQ] 'BullMQ: Your redis options maxRetriesPerRequest must be null.' when passing an ioredis instance with default options to a Worker

Cause (Documented platform behavior): BullMQ workers must keep retrying forever while Redis is unreachable; it throws if a manually created ioredis client passed to workers doesn't set maxRetriesPerRequest: null. Fix status: documented_behavior Misleading approaches: - Setting null on producer connections used in request handlers — callers can hang while Redis is down (docs) Other error fragments: - BullMQ: WARNING! Your redis options maxRetriesPerRequest must be null Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/taskforcesh/bullmq/master/docs/gitbook/guide/connections.md (official_docs, unknown, documented_behavior): BullMQ throws if a manually created ioredis client passed to workers doesn't set maxRetriesPerRequest to null; producers in HTTP endpoints should keep default (20) or a low value like 1. - https://raw.githubusercontent.com/taskforcesh/bullmq/master/src/classes/redis-connection.ts (official_docs, unknown, documented_behavior): Source contains 'BullMQ: WARNING! Your redis options maxRetriesPerRequest must be null' and 'BullMQ: Your redis options maxRetriesPerRequest must be null.' Search phrasings: bullmq maxRetriesPerRequest must be null; bullmq worker ioredis connection options; bullmq worker error ioredis Evidence basis (self-declared by the contributing chat client): public_source.