Wait step didn't trigger webhook | Community
Skip to main content
Melody_Frieda1
Melody_Frieda1
New Participant
September 13, 2018
Solved

Wait step didn't trigger webhook

  • September 13, 2018
  • 1 reply
  • 4207 views

Hi,


I tried getting Marketo support help with this (with no success), but I've found the Community to be much more knowledgable in troubleshooting everything Marketo! Love you guys....


I'm trying to accomplish the following:

  1. Step 1: When a data value changes it triggers the first SMS webhook
    1. This was done successfully in my test
  2. Step 2: Wait 24 hours, can end any day, and must end at 8am PDT
    1. In my test, the first trigger was fired off at 2:51pm PDT
  3. Step 3: Fire next SMS webhook
    1. 8am the following day, the webhook did not fire
  4. Step 3: Wait 6 hours, can end any day, and must end at 2pm PDT
    1. etc. I've attached the smart campaign flow for review

Here is a snapshot of what I want the flow to look like for the first 36 hours. The first SMS webhook is called, then I want to wait until 8am the following day (regardless of the time the lead's first webhook fired the prior day) then send the next SMS webhook at exactly 8am the next day

I can't create a batch smart campaign because webhooks are called via triggered smart campaigns only. Marketo Support told me to remove the wait step duration (e.g. 24 hours), which resulted in all of my SMS webhooks firing at once

What am I doing wrong here? Please help!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Steven_Vanderb3

Sounds like a timing issue.  Assuming the same scenario were run today, 9/13....

9/13, 2:51PM PDT: First flow step is processed and enter wait step

9/14, 2:51PM PDT: 24 hours is up, but must end at 8AM which will be tomorrow

9/15 8:00AM PDT: Come out of wait step, process next webhook, and enter next wait step

9/15: 2:00PM PDT: Come out of the wait step and process the last webhook.

However the above is the ideal which will probably never happen.  Coming out of a wait step is a low priority action and will defer to other, higher priority trigger actions running at the same time.  For your wait step "Wait 6 hours, must end at 2PM", it assumes that the lead come out of the previous wait step (and finish processing the previous webhook) at exactly 8AM.

The more likely type of run you would see is something like this

9/13, 2:51PM PDT: First flow step is processed and enter wait step

9/14, 2:51PM PDT: 24 hours is up, but must end at 8AM which will be tomorrow

9/15 8:10AM PDT: Come out of wait step, process next webhook, and enter next wait step.  The campaign had to wait for higher priority tasks to finish before it could process the webhook between the two wait steps.

9/15: 2:10PM PDT: 6 hours is up but must end at 2PM which will be tomorrow

9/16: 2:00PM PDT: Come out of the wait step and process the last webhook.

You could use recurring batch campaigns that run at scheduled time with a flow step to request your trigger campaigns with the webhooks rather than rely on the wait steps if you want to use specific timing.

Trigger Campaign 1:  Sends the first webhook when the data value changes

Batch Campaign 1: At 8:00 AM, Request Trigger Campaign A for all people that got the SMS message from Trigger Campaign 1

Trigger Campaign A: Send SMS message

Batch Campaign 2: At 2:00PM, Request Trigger Campaign B for all people that got the SMS message from Trigger Campaign A

Trigger Campaign B: Send SMS message

1 reply

Steven_Vanderb3
Steven_Vanderb3Accepted solution
New Participant
September 13, 2018

Sounds like a timing issue.  Assuming the same scenario were run today, 9/13....

9/13, 2:51PM PDT: First flow step is processed and enter wait step

9/14, 2:51PM PDT: 24 hours is up, but must end at 8AM which will be tomorrow

9/15 8:00AM PDT: Come out of wait step, process next webhook, and enter next wait step

9/15: 2:00PM PDT: Come out of the wait step and process the last webhook.

However the above is the ideal which will probably never happen.  Coming out of a wait step is a low priority action and will defer to other, higher priority trigger actions running at the same time.  For your wait step "Wait 6 hours, must end at 2PM", it assumes that the lead come out of the previous wait step (and finish processing the previous webhook) at exactly 8AM.

The more likely type of run you would see is something like this

9/13, 2:51PM PDT: First flow step is processed and enter wait step

9/14, 2:51PM PDT: 24 hours is up, but must end at 8AM which will be tomorrow

9/15 8:10AM PDT: Come out of wait step, process next webhook, and enter next wait step.  The campaign had to wait for higher priority tasks to finish before it could process the webhook between the two wait steps.

9/15: 2:10PM PDT: 6 hours is up but must end at 2PM which will be tomorrow

9/16: 2:00PM PDT: Come out of the wait step and process the last webhook.

You could use recurring batch campaigns that run at scheduled time with a flow step to request your trigger campaigns with the webhooks rather than rely on the wait steps if you want to use specific timing.

Trigger Campaign 1:  Sends the first webhook when the data value changes

Batch Campaign 1: At 8:00 AM, Request Trigger Campaign A for all people that got the SMS message from Trigger Campaign 1

Trigger Campaign A: Send SMS message

Batch Campaign 2: At 2:00PM, Request Trigger Campaign B for all people that got the SMS message from Trigger Campaign A

Trigger Campaign B: Send SMS message

Melody_Frieda1
Melody_Frieda1Author
New Participant
September 13, 2018

@Steven Vanderberg Thanks for the reply! I thought webhooks cannot be triggered via a batch campaign? I tried that a couple weeks ago and got a response code of 1000:

http://developers.marketo.com/webhooks/errors/

Steven_Vanderb3
Steven_Vanderb3
New Participant
September 13, 2018

Batch campaigns can't, but they CAN use Request Campaign flow step to trigger a Trigger campaign that has the Webhook flow step.

Terms & ConditionsAccessibility statement

Loading footer...