Hello ​@spencn10 ,

The trigger for a message sequence is always the date and time you set for that sequence. Unlike a standard workflow, where you configure triggers to start the flow, in sequences you specify after how many hours or days each step should be sent. Therefore, you don’t need to configure any triggers within the flow itself.

See the example sequence below: I have four flows scheduled at different times. Individually, none of the flows contain triggers; when the configured date and time arrive, that flow is automatically sent to the customer added to the sequence.

 

​@rogerioaraujo It seems like you mentioned you don’t have any “triggers” within each sequence, but that is my problem haha. Can you just have “the message” without the trigger inside of the sequence?

Because I have them scheduled just like you show, but it seems to double fire still.

When you set up each sequence to be sent, you specify how long after the previous step it should go out: immediately or after a certain number of days.
Then you add additional sequences and define the delay relative to the previous send for each one.
Essentially, each sequence will be sent at the date and time you scheduled.

Here are some details that might hint at the problem:
Is the same message being sent twice, or is the second message — which should go out later — being sent too early? If so, the sequence may be configured as “immediate send” when you actually need to set an additional day delay.

If the identical message is sent twice at the same time, review your flow: check the logic to see if an error is causing the contact to be triggered twice. For example, one step in the flow might be unintentionally adding the contact to another sequence.