Can't delete failing messages

[jkazimierczak-eficode]

Hey! I cannot delete failing messages. It seems that for some reason we got messages displayed as null.null as source table. Commited at shows start of the epoch:

These are the ones that are failing to be delivered. Other messages with correct attributes (actual schema.table names, and correct commited at timestamps) are delivered and acked correctly.

We have around 2K failing messages, and clearing them through this view doesn't work. Contrary to discarding just failing ones, discarding all messages works for messages that would go through just fine, but it doesn't clear the failing ones.

We're using v0.13.21.

[dosubot]

Hi @jkazimierczak-eficode! I'm Dosu and I’m helping the sequin team.

This looks like a known bug in v0.13.21. The null.null table name and epoch timestamp symptoms are specific to that version, and the inability to discard failing messages is also part of the same set of bugs.

These issues were fixed in commits after v0.13.21. Upgrading to a newer version should resolve this.

If you need an immediate workaround before upgrading, you may be able to manually delete the stuck messages directly from the sequin_streams.consumer_events database table, though upgrading is the recommended solution.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[jkazimierczak-eficode]

It seems related, so I'll try that out and get back with the results here.