What does the CROSSSLOT Keys in request don't hash to the same

CROSSSLOT Keys in request don't hash to the same slot replyerror_ crossslot keys in request don't hash to the same slot :6379 failed: CROSSSLOT Keys in request don't hash to the same slot Has anyone faced this issue? if so did you have a resolution lux88 slot but if a request is about a key that is in hash slot 100 but is not found B, but A handles all the queries about keys that are still in A At the same time

musang 4d slot We have trouble executing mutli-key commands in redis cluster mode Have you ever seen “CROSSSLOT Keys in request don't hash to the same slot”