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). ConnectTimeout, command=EVAL, timeout: 5000, inst: 0, qu: 6, qs: 0, aw: False, bw: CheckingForTimeout, last-in: 0, cur-in: 0, sync-ops: 0, async-ops: 928677, serverEndpoint: 10.240.0.11:8506, conn-sec: n/a, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: actions-job-agent-65b75f8d86-rmz8p(SE.Redis-v2.6.111.64013), PerfCounterHelperkeyHashSlot: 3025, IOCP: (Busy=0,Free=1000,Min=32,Max=1000), WORKER: (Busy=6,Free=32761,Min=96,Max=32767), POOL: (Threads=71,QueuedItems=0,CompletedItems=666200235), 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). ConnectTimeout, command=EVAL, timeout: 5000, inst: 0, qu: 6, qs: 0, aw: False, bw: CheckingForTimeout, last-in: 0, cur-in: 0, sync-ops: 0, async-ops: 928677, serverEndpoint: 10.240.0.11:8506, conn-sec: n/a, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: actions-job-agent-65b75f8d86-rmz8p(SE.Redis-v2.6.111.64013), PerfCounterHelperkeyHashSlot: 3025, IOCP: (Busy=0,Free=1000,Min=32,Max=1000), WORKER: (Busy=6,Free=32761,Min=96,Max=32767), POOL: (Threads=71,QueuedItems=0,CompletedItems=666200235), 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). ConnectTimeout, command=EVAL, timeout: 5000, inst: 0, qu: 6, qs: 0, aw: False, bw: CheckingForTimeout, last-in: 0, cur-in: 0, sync-ops: 0, async-ops: 928677, serverEndpoint: 10.240.0.11:8506, conn-sec: n/a, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: actions-job-agent-65b75f8d86-rmz8p(SE.Redis-v2.6.111.64013), PerfCounterHelperkeyHashSlot: 3025, IOCP: (Busy=0,Free=1000,Min=32,Max=1000), WORKER: (Busy=6,Free=32761,Min=96,Max=32767), POOL: (Threads=71,QueuedItems=0,CompletedItems=666200235), 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). ConnectTimeout, command=EVAL, timeout: 5000, inst: 0, qu: 6, qs: 0, aw: False, bw: CheckingForTimeout, last-in: 0, cur-in: 0, sync-ops: 0, async-ops: 928677, serverEndpoint: 10.240.0.11:8506, conn-sec: n/a, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: actions-job-agent-65b75f8d86-rmz8p(SE.Redis-v2.6.111.64013), PerfCounterHelperkeyHashSlot: 3025, IOCP: (Busy=0,Free=1000,Min=32,Max=1000), WORKER: (Busy=6,Free=32761,Min=96,Max=32767), POOL: (Threads=71,QueuedItems=0,CompletedItems=666200235), 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). ConnectTimeout, command=EVAL, timeout: 5000, inst: 0, qu: 6, qs: 0, aw: False, bw: CheckingForTimeout, last-in: 0, cur-in: 0, sync-ops: 0, async-ops: 928677, serverEndpoint: 10.240.0.11:8506, conn-sec: n/a, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: actions-job-agent-65b75f8d86-rmz8p(SE.Redis-v2.6.111.64013), PerfCounterHelperkeyHashSlot: 3025, IOCP: (Busy=0,Free=1000,Min=32,Max=1000), WORKER: (Busy=6,Free=32761,Min=96,Max=32767), POOL: (Threads=71,QueuedItems=0,CompletedItems=666200235), 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)

62..@dynamic_table_start + length - 1 inside guards requires an explicit step, please write 62..@dynamic_table_start + length - 1//1 or 62..@dynamic_table_start + length - 1//-1 instead

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

62..@dynamic_table_start + length - 1 inside guards requires an explicit step, please write 62..@dynamic_table_start + length - 1//1 or 62..@dynamic_table_start + length - 1//-1 instead

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it