Put a contact limit on Send To Somebody Else actions

[rowanseymour]

Start Somebody Else In a Flow has been limited to 1 contact for a while now to prevent cascading flow starts.

Maybe there should be a limit on broadcasts created in flows to? There's not he same danger of cascades, but there is the same problem that users don't fully understand that if they start Group 1 in a flow and then from flow message Group 1, each contact gets a message for each contact in that group.

There's also the implementation detail that these broadcasts are non-persistent (not in the database) so wouldn't be monitorable or interruptable.

Limit could be generous... 100.. 1000

[ericnewcomer]

I'm fine with a limit so long as it's reasonably big. I think 1,000 is fair here. How do we message this to the users since this is a runtime failure. If it targets more than 1,000 just it just fail entirely and nobody gets it? That might be preferable to truncation of that recipient list.

[rowanseymour]

I think it's the same as Start Flow.. we explain the limit on the action UI, and then we limit the query. First 1000 get the broadcast.

[github-actions]

Without activity, this issue will be closed in 14 days.