Hi @camiscn 

Good question.

We would need to see detailed screenshots with how your Zap steps are configured to have enough context.

@camiscn 

We would need to see screenshots for all the Zap steps to have full context.

Does this work?

@camiscn 

Can you show a specific example with screenshots from Slack of the issue?

The message is sent in the thread but also to the channel as a new message

@camiscn 

This is a Slack notification saying there was a thread reply.

Can’t say for sure but it may be related to the Schedule At field you have set.

OBSERVATION

All of the Formatter steps could likely be optimized to use 1 Code step to save Zap Tasks.

@camiscn

This is a Slack notification saying there was a thread reply.

 

Can’t say for sure but it may be related to the Schedule At field you have set.

 

OBSERVATION

All of the Formatter steps could likely be optimized to use 1 Code step to save Zap Tasks.

That was! It no longer sends the message to the channel!

Thank you Troy

Thanks for following up here @camiscn. Really appreciate you coming back here to confirm Troy’s suggestion of removing the value in the Schedule At field here did the trick! 

Seems like you’re all set for now but please do reach out in the Community again if you run into any further Zap issues. In the meantime, happy Zapping!