Duplicate messages received on Slack channel from Google form

[wpskier]

Your Task History ID

IjU3NjUwNTY4MDYzMzA0M2M1MjY0NTUzMzUxMzI1MTY1NTQzOTBmMzYi_pc

I just created a new workflow to post a message in a Slack channel when a user completes a Google form. It works great, except that I get two messages in the Slack channel. One message is formatted as expected based on the "Message" field in the Slack action. But the other message just contains the form answers all concatenated together, with no spaces between the fields:

For example, the bad message looks like:
John [email protected] 1YesYes138.34YesNo

I've deleted the Slack action and re-created it, and I'm still getting the same behavior.

How can I stop the second, incorrect message?

Thanks!

 

[Soumya Tripathi]

Hello @wpskier
As we can see in the Task History, previously you added 2 action steps of "Slack : Send Channel Message". For the second action step, the message text that was being sent was, for example,
"Richard [email protected], Sm'D carabiners (4)138.87YesYesYeshttps://drive.google.com/open?id=1hT1xjnM2YDLU0v4_w9xJv3gLw7KpgTeP",
therefore 2 messages were being sent. Now that you have deleted the second action step of "Slack : Send Channel Message", you can do 2–3 test submissions to see if it's working fine.

 

[wpskier]

Hello @wpskier
As we can see in the Task History, previously you added 2 action steps of "Slack : Send Channel Message". For the second action step, the message text that was being sent was, for example,
"Richard [email protected], Sm'D carabiners (4)138.87YesYesYeshttps://drive.google.com/open?id=1hT1xjnM2YDLU0v4_w9xJv3gLw7KpgTeP",
therefore 2 messages were being sent. Now that you have deleted the second action step of "Slack : Send Channel Message", you can do 2–3 test submissions to see if it's working fine.

I never had two actions in my workflow. I even tried deleting the one Slack action and re-creating it, but it didn't resolve the issue.

 

[wpskier]

I re-created the workflow and it's working as expected now. You can disregard this issue.

 

[ArshilAhmad]

Thank you for the update. We're happy to hear that it's working now