I like to set up workflows to perform specific functions and then chain together multiple workflows for more complex functions. This allows my workflow logic to be more modular and reusable, allowing me to use the same function in multiple workflows and only need to change the function once for it to affect all of my workflows. As this is a common best practice I must imagine many other developers in ReTool do something similar.
However, because of the way workflows are billed, this gets really expensive because each component workflow run as part of a compound workflow counts as a successful workflow run. Say I have a workflow that calls four other workflows, each time that workflow runs, it would count as five workflow runs (one for the compound workflow, four for the components).
Does anyone know of a better way to develop with modular logic like this but not needlessly run up the workflow bill? This billing design incentivizes users to write all of the logic explicitly in each workflow - as a result you pay less if you make it harder for yourself to use Retool.
