Sipke Schoorstra

Hello @faith0831 , thank you for submitting a PR. Can you explain what the issue is and how this PR fixes that? I noticed that it removes the use of...

@mohdali I see, thanks for the clarification. We shouldn't drop paging support because it might negatively impact other users that use other database servers and where doing a batched deletion...

@faith0831 @mohdali Should we keep this PR open, change it to Draft, or abandon?

Hi @whoiscxt-zishu , thank you for bringing this to my attention. I tried a simple workflow with the ForEach activity to see if I could reproduce the behavior that you...

No worries! I tried your suggestion, and now the first iteration will be blocked (as expected). Here's what the journal looks like: To me this looks according to spec, but...

Doing the Delay in the iteration doesn't seem to cause any issues that I can see, either: And the body of the ForEach: I could be totally missing something here....

PS. I'm going to go ahead and close this issue as "cannot reproduce", but please let me know if I need to reopen it when you have repro steps. Thank...

@kivocsa99 Sure, the workaround is to retry the call to `await _connection.start()`. I think I did it in a loop with a small delay.

@karavajka Should we close this PR?

Got it. Although we can't just undo this change as it would then break users using the new bookmark names, what we might do is look for both names. This...