Troubleshooting Inconsistent Hubspot Form Trigger in Workflow

This topic was automatically generated from Slack. You can find the original thread here.

Hi everyone! I’m having trouble with a workflow triggered by a Hubspot form submission… for some reason the workflow doesn’t trigger every time the form is submitted and of the 20 or so submissions it’s captured about 2. It’s using the default form trigger, does anyone have a minute to help me troubleshoot? I’d really appreciate it.

Hello , thanks for raising this. I’ll try to reproduce this and let you know

Amazing! Thank you Leo! :tada:

Hey , any luck replicating the issue? :smile:

I’m still figuring it out. I’ll get back to you in the next 1 hour

You’re a saint, thank you! :raised_hands:

Hello , I can’t seem to reproduce your issue. Steps I have teaken:

  1. I create a new Hubspot New form submission with 15 seconds interval
  2. Then I created about 16 form submission during 10 minutes
  3. I observed that all of my form submission emit new events on Pipedream source
    @U05065WUZ1C would you mind sharing more detail on your hubspot form?

Including @UR84EMEUT in the loop, she’s our component dev and have context on this. @UR84EMEUT when you have time, could you advice some insights?

Here’s my hubspot form submissions

Hi , interesting, thanks so much for the help on this again! Here’s some screenshots of my form setup

Thanks , would you mind sharing the events you have received?

Sure, here you go! Could always set up a new one, but would love to know why it’s failing :smile:

may I ask if you’re on free plan or paid plan?

Paid :smile: Although, I setup the workflow before I paid :slightly_smiling_face:

I see, I asked because maybe the source with 15 seconds interval may consume all of your invocation/credit for free plan. Hence, there’s no event on that day.

Could you try to submit a test form to see if the source works emit new event?

Sure, so just fill out the form as a test?

Yeah fill out the form as a test

Cool just done, no luck

Btw just noticed this

Can’t seem to see the trigger in the deployment is that normal?