SCAN Command - Cursor always returns 0

The SCAN command when run on KeyDB always returns 0 though there are over 100 keys in the DB which match the pattern and the the COUNT is set to 10;

KEYS OUTPUT

127.0.0.1:6379> KEYS terminal*
   1) "terminal:661"
  2) "terminal:731"
  3) "terminal:630"
  4) "terminal:349"
  5) "terminal:202"
  6) "terminal:717"
  7) "terminal:446"
  8) "terminal:692"
  9) "terminal:456"
 10) "terminal:584"
 11) "terminal:192"
 12) "terminal:498"
 13) "terminal:769"
 14) "terminal:128"
 15) "terminal:695"
 16) "terminal:608"
 17) "terminal:138"
 18) "terminal:678"
 19) "terminal:495"
 20) "terminal:701"
 21) "terminal:344"
 22) "terminal:549"
 23) "terminal:583"
 24) "terminal:632"
 25) "terminal:239"
 26) "terminal:232"
 27) "terminal:531"
 28) "terminal:459"
 29) "terminal:597"
 30) "terminal:532"
 31) "terminal:131"
 32) "terminal:506"
 33) "terminal:19"
 34) "terminal:354"
 35) "terminal:331"
 36) "terminal:691"
 37) "terminal:330"
 38) "terminal:423"
 39) "terminal:145"
 40) "terminal:567"
 41) "terminal:683"
 42) "terminal:247"
 43) "terminal:730"
 44) "terminal:764"
 45) "terminal:439"
 46) "terminal:621"
 47) "terminal:729"
 48) "terminal:590"
 49) "terminal:78"
 50) "terminal:29"
 51) "terminal:248"
 52) "terminal:323"
 53) "terminal:645"
 54) "terminal:181"
 55) "terminal:245"
 56) "terminal:762"
 57) "terminal:148"
 58) "terminal:576"
 59) "terminal:617"
 60) "terminal:700"
 61) "terminal:551"
 62) "terminal:508"
 63) "terminal:134"
 64) "terminal:565"
 65) "terminal:225"
 66) "terminal:149"
 67) "terminal:765"
 68) "terminal:615"
 69) "terminal:634"
 70) "terminal:689"
 71) "terminal:602"
 72) "terminal:208"
 73) "terminal:627"
 74) "terminal:675"
 75) "terminal:150"
 76) "terminal:526"
 77) "terminal:631"
 78) "terminal:716"
 79) "terminal:588"
 80) "terminal:385"
 81) "terminal:723"
 82) "terminal:207"
 83) "terminal:705"
 84) "terminal:405"
 85) "terminal:243"
 86) "terminal:421"
 87) "terminal:227"
 88) "terminal:610"
 89) "terminal:636"
 90) "terminal:573"
 91) "terminal:325"
 92) "terminal:146"
 93) "terminal:422"
 94) "terminal:295"
 95) "terminal:407"
 96) "terminal:438"
 97) "terminal:435"
 98) "terminal:199"
 99) "terminal:690"
100) "terminal:304"

Truncated: over 300 terminal KEYS

SCAN OUTPUT

127.0.0.1:6379> SCAN 0 MATCH terminal* COUNT 10

  1. “0”
    1. “terminal:131”
    2. “terminal:278”

** INFO **

# Server
redis_version:6.0.11
redis_git_sha1:59279d36
redis_git_dirty:0
redis_build_id:40014c9a497469de
redis_mode:standalone
os:Linux 5.4.0-1029-aws x86_64
arch_bits:64
multiplexing_api:epoll
atomicvar_api:atomic-builtin
gcc_version:7.5.0
process_id:907
run_id:4279cfffbd7c9435f99fc91890581952a142189b
tcp_port:6379
uptime_in_seconds:17376
uptime_in_days:0
hz:10
configured_hz:10
lru_clock:10673531
executable:/usr/bin/keydb-pro-server
config_file:/etc/keydb/keydb.conf

This may be specific to the KEYDb Pro instances created by AWS marketplace, as a new instance with a manual install did not have this issue.