Triggering escrow via Rules leads to WSOD in drupal 10

Thanks a lot Aporie for your extra fast reply.

I tried on a fresh D10.2 installation and had the exact same issue.

Trying to rebuild the rule also doesnt work. In Rules, the transaction action is done in two steps:
1- Add action "Create a new transaction entity" --> This works as before
2- Add action "Perform transaction" --> This is not possible anymore, when this action is selected in the available actions list (in Rules UI), there is an immediate WSOD.
If on your side you could not create the transaction, maybe it was because you missed step 2? Or didn't you experience this WSOD when selecting the "Perform transaction" action as I do?

To note that the only thing that has changed in my setup is the upgrade Drupal 9.5-->Drupal 10.2 (my Rules and CF modules were already at their latest version far before doing this upgrade and everything worked perfectly at that time). Also I did not have any issues appeared with my other rules. This leads me to think that the problem is probably linked to the RulesAction plugin of commerce_funds, which should somehow adapt something to work on D10?

I was not aware about the transaction fields that have been added, so thanks for the info. However and unless I missed something I could only find a field for doing transfers. My use case only uses escrow payments (which is a transaction offered by the commerce_funds module), as I need to have money exchanges between users retained between two workflow points: User A requests something to user B and initiates an escrow (the money is withdrawn from his account), then User B does what user A has requested, and only after User A confirms the User B achieved the requested task the money is credited on User B account (escrow finalzed). Is there a way using this transaction fields to retain a payment in the way described above (meaning to have a kind of escrow field)?

Thanks again

Thanks a lot, the patch works like a charm and solves the issue.
May this help regarding your two points:
1. Indeed, Rules UI will not accept a price field (number) as it requires a decimal input. Three possible workarounds: Either to import a rule configuration with the node.field_amount.number in the YAML code (this will bypass the data type check and the rule will work perfectly) or convert the price field into a decimal value (rules offers data conversion actions), or use directly a decimal field instead of price field (note that I didn't test this 3rd option).
For the currency, I do not have any trouble, I simply enter the currency code string (e.g "EUR") into the currency field and it works. Take care to enter it in "direct input mode", and not "data selection mode"

2. What you should do is:
a- Add an action "Create a transaction entity" and fill in the necessary fields: type, issuer, recipient, brut amount, currency, payment method, currency and status. In my case, I assign as well a hash (equal to my node uuid) and I leave net amount and fees fields blank (automatically calculated using the commerce_funds modules settings).
b- Add an action "Save entity", select commerce_funds_transaction_created (or the rules variable name you have assigned if you modified it at the step before), and put "1" in "Force saving immediately"
c- Add an action "Perform transaction" by selecting "commerce_funds_transaction_created" (or your rules variable name if you modified it at step a) in the data selector.
With this it should normally work (the transaction should be visible in the commerce_funds view showing all site transactions and user balances are updated accordingly.
If following these steps does not work for you, do not hesitate to share screenshots or additionnal info so that I can support you finding what goes wrong (I know that the Rules interface is a bit picky). Combining commerce_funds with Rules is really powerful and this interface should be kept in my opinion.

Regarding the transaction fields this is definitely a great feature covering most probably a large number of use cases, but unfortunately not mine. Indeed, Rules will not allow any action on this field, as at the time the Rule is triggered the entity referenced by the field is not created (I have spent my day testing it with all possible twists I know, but without success).

Hoping it helps you as well in return!
Thanks again