Bug report

What Debezium connector do you use and what version?

debezium-connector-ibmi

What is the connector configuration?

can be supplied

What is the captured database version and mode of deployment?

E.g. on-premises, with a specific cloud provider, etc.

DB2 on ibmi

What behavior do you expect?

stream all events

What behavior do you see?

It occasionally gets stuck saying it can't retrieve a sequence on a given receiver
The sequence number is indeed ouside the range for the receiver when investigated

Do you see the same behaviour using the latest released Debezium version?

Ideally, also verify with the latest Alpha/Beta/CR version.

Yes

Do you have the connector logs, ideally from start till finish?

You might be asked later to provide DEBUG/TRACE level log.

Logs can be provided

How to reproduce the issue using our tutorial deployment?

Not easily reproducible
Other clients have reported the same problem

There are two candidates for this:
1/ The end sequence calcuation in ReceiverPagination
2/ The ibmi API returning an incorrect continuation offset

Typically recievers are set to have a high number of entries in them so the complexity in ReceiverPagination to allow the request to span receivers is probably not required. This should simplify the code and should also mean the API is unlikely to return the wrong receiver in the continuation offset.