We just published significant updates to the main App Editor article on Triggers. Therein you will see new info related to Trigger timeouts and trigger (table action) retries as of r332 and LTS15, as well as more information explaining the Trigger Queue and Errors.
@Tim_Reblitz This is probably one of the greatest addition to the Tulip documentation I’ve seen lately! Content is quite interesting and useful. It’s great to see the basics of fundamental app mechanics finally covered in such a level of details.
If I understand/guessing correctly, if I see an action storing aggregation value to a record place holder the value stored will be …
If the actions are bundled, the value is taken before the the create/load action
If the actions are not bundles, the value is taken just before the store action.
I think this is counter intuitive.
To make this intuitive, I think the trigger editor should at least visually show which actions are going to be bundled, and warn the app builders by highlighting the aggregation inside the bundled action.