Unexpected usage of out-of-box "Notify: Join Conference Call Via SMS" workflow, which has new "Send SMS response" activities since Quebec, may cause high/loop SMSDescription"Notify: Join Conference Call Via SMS" workflow has new "Send SMS response" activities since Quebec. This is an intended design change in this OOB demo workflow. And this workflow is intended to be used as Incoming SMS Workflow in Notify Group. We do not expect this workflow to be used as Outgoing SMS Workflow in Notify group, but we noticed in some customer's instance, this OOB demo workflow is populated as Outgoing SMS Workflow. However, this may cause high SMS usage, because this OOB demo workflow was incorrectly used in Notify Group as Outgoing SMS workflow. In this workflow, when "Valid conference call?" activity result is No, it may cause this workflow to trigger in loop.Release or EnvironmentQuebec or laterResolutionPlease do not use this OOB demo workflow "Notify: Join Conference Call Via SMS" as Outgoing SMS workflow in Notify Group records. The Outgoing SMS workflow is intended to have some customised workflow to perform additional jobs while SMS' are sent. E.g. add a log in the instance, send a Slack/Team message at the same time and etc.. Sending another SMS in Outgoing SMS workflow will trigger the workflow in loop, then result in high SMS usage and cost.