Skip to main content

This has been a topic of debate amongst the developers that I work with. Many of them are against using the process composer to sequentially call and instead would prefer to call a single main task bot from the process composer and that main bot would call all child task bots

Their main argument for this is that when task bots are called via the process composer, another task bot from a different process with a higher priority can potentially interrupt the work flow and trigger before the first process finishes execution. If that is true, then it seems to me like using the process composer in an environment where other task bots are scheduled close by could cause risks if the workflow has the risk of being interrupted.

What are other people’s thoughts on this? And is there a workaround to prevent other bots from triggering in-between the process composer task bots?

Be the first to reply!

Reply