The end user experience might come not so ideal in case of applying a custom site design e.g seeing waiting for progress state in case of simple action e.g. adding to a hub site with 10sec to 3min and then as a last action triggering flow which immediately results. It might causes a meaning the whole operation is finished and further confusions like "Is it/ or is it not finished yet?" Could it be so that:
1) the platform offers e.g. runFlow with a timeout parameter (in future possibly also a nice way showing to end user actual time to the timeout exceed)

(or alternatively the triggerFlow verb with parameter timeout in meaning awaiting the flow till the timeout/ without the timeout parameter works as it is working now)

2) If only there will be chance to add custom descriptive text(s) to inform the end user to mitigate that confusions mentioned above. That custom description could be:
a) at the bottom level
b) as the (i) for each particular verb level