The message timed out in the backlog attempting to send because no connection became available (5000ms) - Last Connection Exception: It was not possible to connect to the redis server(s). There was an authentication failure; check that passwords (or client certificates) are configured correctly: (IOException) Unable to read data from the transport connection: Connection reset by peer. ConnectTimeout, command=EVAL, timeout: 5000, inst: 0, qu: 5, qs: 0, aw: False, bw: CheckingForTimeout, rs: NotStarted, ws: Initializing, last-in: 0, cur-in: 0, sync-ops: 0, async-ops: 712271, serverEndpoint: actions-production.centralus.redisenterprise.cache.azure.net:10000, conn-sec: n/a, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: actions-job-agent-b9576f665-cbdjx(SE.Redis-v2.6.111.64013), PerfCounterHelperkeyHashSlot: 12847, IOCP: (Busy=0,Free=1000,Min=32,Max=1000), WORKER: (Busy=7,Free=32760,Min=96,Max=32767), POOL: (Threads=28,QueuedItems=0,CompletedItems=503775282), v: 2.6.111.64013 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)

The message timed out in the backlog attempting to send because no connection became available (5000ms) - Last Connection Exception: It was not possible to connect to the redis server(s). There was an authentication failure; check that passwords (or client certificates) are configured correctly: (IOException) Unable to read data from the transport connection: Connection reset by peer. ConnectTimeout, command=EVAL, timeout: 5000, inst: 0, qu: 5, qs: 0, aw: False, bw: CheckingForTimeout, rs: NotStarted, ws: Initializing, last-in: 0, cur-in: 0, sync-ops: 0, async-ops: 712271, serverEndpoint: actions-production.centralus.redisenterprise.cache.azure.net:10000, conn-sec: n/a, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: actions-job-agent-b9576f665-cbdjx(SE.Redis-v2.6.111.64013), PerfCounterHelperkeyHashSlot: 12847, IOCP: (Busy=0,Free=1000,Min=32,Max=1000), WORKER: (Busy=7,Free=32760,Min=96,Max=32767), POOL: (Threads=28,QueuedItems=0,CompletedItems=503775282), v: 2.6.111.64013 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)

The message timed out in the backlog attempting to send because no connection became available (5000ms) - Last Connection Exception: It was not possible to connect to the redis server(s). There was an authentication failure; check that passwords (or client certificates) are configured correctly: (IOException) Unable to read data from the transport connection: Connection reset by peer. ConnectTimeout, command=EVAL, timeout: 5000, inst: 0, qu: 5, qs: 0, aw: False, bw: CheckingForTimeout, rs: NotStarted, ws: Initializing, last-in: 0, cur-in: 0, sync-ops: 0, async-ops: 712271, serverEndpoint: actions-production.centralus.redisenterprise.cache.azure.net:10000, conn-sec: n/a, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: actions-job-agent-b9576f665-cbdjx(SE.Redis-v2.6.111.64013), PerfCounterHelperkeyHashSlot: 12847, IOCP: (Busy=0,Free=1000,Min=32,Max=1000), WORKER: (Busy=7,Free=32760,Min=96,Max=32767), POOL: (Threads=28,QueuedItems=0,CompletedItems=503775282), v: 2.6.111.64013 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)

The message timed out in the backlog attempting to send because no connection became available (5000ms) - Last Connection Exception: It was not possible to connect to the redis server(s). There was an authentication failure; check that passwords (or client certificates) are configured correctly: (IOException) Unable to read data from the transport connection: Connection reset by peer. ConnectTimeout, command=EVAL, timeout: 5000, inst: 0, qu: 5, qs: 0, aw: False, bw: CheckingForTimeout, rs: NotStarted, ws: Initializing, last-in: 0, cur-in: 0, sync-ops: 0, async-ops: 712271, serverEndpoint: actions-production.centralus.redisenterprise.cache.azure.net:10000, conn-sec: n/a, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: actions-job-agent-b9576f665-cbdjx(SE.Redis-v2.6.111.64013), PerfCounterHelperkeyHashSlot: 12847, IOCP: (Busy=0,Free=1000,Min=32,Max=1000), WORKER: (Busy=7,Free=32760,Min=96,Max=32767), POOL: (Threads=28,QueuedItems=0,CompletedItems=503775282), v: 2.6.111.64013 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)