ConnectionBus: Transaction X aborted due to timeout

0
Hello, I have in a microflow a java action that can last a long time (it's a file conversion and I use a external library so I cannot modify it...). When the conversion exceeds than 10 minutes, it fails with the error: "ConnectionBus: Transaction X aborted due to timeout" The execution then stops, and my file isn't converted. Is it possible to modify the value of this timeout or do you have an idea to make it work? thanks in advance
asked
1 answers
0

Hi Vincent,

To my knowledge you can’t “just increase” that timeout in Mendix Cloud. The ~10-minute DB transaction limit will abort long-running actions. And I wouldn't recommend it if it was possible either...

Make it work by removing the long task from the request/transaction:

  1. Run the conversion asynchronously:

    • Use Task Queue (Mendix 10) or CommunityCommons executeMicroflowInBackground.

  2. Ensure the Java action doesn’t touch Mendix objects while converting:

    • Read needed data (e.g., file path/bytes) up front, then convert outside any transaction.

    • After it finishes, open a short microflow/transaction to save the result.

  3. For very long/CPU-heavy work, offload to an external worker/service and poll or use a callback.

On-prem you might tweak server transaction settings, but it’s not recommended. The robust fix is: async + no open transaction during the heavy Java work.

answered