I have a relatively simple workflow as depicted next:

When I use MongoDB persistence in my Quarkus app, the workflow execution gets stuck on the step indicated with the red arrow (i.e. just before entering the sequential multi-instance subprocess). There is nothing on the logs (switched to TRACE) and my own logs indicate that "Find groups" service was executed successfully. Kogito MongoDB collections for my workflow seem to have been created properly and are populated with runtime data.

If I remove persistence, using the in-memory one, the workflow works fine.

I could prepare a sample project to test this in isolation but wanted to ask first if this happens to be a known issue or if someone else is already using successfully multi-instance sequential subprocesses with MongoDB persistence?