I would be more flexible to adjust the timeout of based on constant value.
So we do not need to pack, deploy and restart the mission-critical API every time we change the the timeout duration.
Thank you, @Panayu, for this idea!
It has been implemented in version 7.15. Like @Johan suggested, it's completely configurable using a microflow expression, so you can use a constant, a variable or whatever else you like.
This is not part of the current roadmap, do you often reconfigure this value?
Make them completely dynamic based on a variable would be even better! But great idea nonetheless!