Dragonfly instead of Redis

[voytech-net]

Hello,

we have a Dragonfly redis cluster which is used for several parts of our app and I wanted to use one of its databases for Outpost. All seems to work correctly, however when delivery fails, no retry is happening and I get error:

{"level":"error","ts":1763825796.3235013,"caller":"services/retrymq_worker.go:37","msg":"retry scheduler monitor error","error":"mismatched message response type: got <nil>, value: <nil>","stacktrace":"github.com/hookdeck/outpost/internal/services.(*RetryMQWorker).Run\n\t/home/runner/work/outpost/outpost/internal/services/retrymq_worker.go:37\ngithub.com/hookdeck/outpost/internal/worker.(*WorkerSupervisor).Run.func1\n\t/home/runner/work/outpost/outpost/internal/worker/supervisor.go:107"} {"level":"error","ts":1763825796.3235526,"caller":"worker/supervisor.go:108","msg":"worker failed","worker":"retrymq-consumer","error":"mismatched message response type: got <nil>, value: <nil>","stacktrace":"github.com/hookdeck/outpost/internal/worker.(*WorkerSupervisor).Run.func1\n\t/home/runner/work/outpost/outpost/internal/worker/supervisor.go:108"}

What should be changed in the Dragonfly setup for this to work, or is Redis a must to have as a service for Outpost to work correctly?

Thank you for your answers.
V.

[alexbouchardd]

Dragonfly is expected to work as it's Redis-compatible. We'll look into it.

[alexluong]

hi there, thanks for your patience, sorry it took us a minute to get around to this. This issue should be resolved in v0.11.0, please check it out and let me know if there's anything else!