A common pattern of broadcast process functions is...
# troubleshooting
n
A common pattern of broadcast process functions is to use the broadcasted state as a mechanism for holding some kind of rule configuration while the non-broadcasted state for the data to be processed against that rule. If you wanted to generate some kind of acknowledgement when a rule was successfully updated or if it failed as a side output of the broadcast element handling, would you get one or more success or failure messages based on the parallelization of that process function?