EXECABORT: EXECABORT Transaction discarded because of previous errors
RedisWhat does it mean?
A transaction in a MULTI/EXEC block was aborted because of errors that occurred during the queueing stage. EXEC rejects the transaction without running any command.
Why does it happen?
A command between MULTI and EXEC contains a syntax error, or errors caught during queueing such as a nonexistent command name or a wrong number of arguments. Such errors invalidate the whole transaction.
How to fix it
Fix the syntax and arguments of the commands in the MULTI block. Check the replies while queueing commands; if any command returns an error instead of QUEUED, the transaction is aborted at EXEC. Rebuild the transaction with valid commands. Note: Redis transactions do not roll back; only queueing errors lead to EXECABORT, and runtime errors do not stop the other commands.
More from this engine
- MOVEDMOVED slot ip:port (cluster redirect)
- ASKASK slot ip:port (cluster redirect)
- NOSCRIPTNOSCRIPT No matching script. Please use EVAL
- NOPERMNOPERM this user has no permissions to run the command or access one of the keys
- ERR value is not an integer or out of rangeERR value is not an integer or out of range
- ERR value is not a valid floatERR value is not a valid float
- ERR increment or decrement would overflowERR increment or decrement would overflow