Best answer

14 minutes delay for Github new commit trigger

  • 4 April 2022
  • 1 reply
  • 119 views

Greetings,

My Zapier integration is as follows:

If my github repo has a new commit, then make a new Asana story.

I’ve used the predefined trigger action.

 

My zap works fine, as you can see below:
 

 

The problem is that I have a delay of 14 minutes.

I have a new commit on March 25, 12:32PM, but Zap starts on March 25, 12:46PM.

Why do I have 14 minutes of delay? Is this a reasonable amount of delay if I used the trigger for ‘Github new commit’? Does anyone experience this amount of delay for ‘Github new commit’ trigger?

icon

Best answer by Troy Tessalone 4 April 2022, 16:15

View original

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

1 reply

Userlevel 7
Badge +14

Hi @Ted_at_Hashsnap 

Good question.

The GitHub New Commit trigger is not instant, and thus depends on your Zapier plan. (see below)

 

Trigger types

There are 2 types of triggers:

  1. Polling trigger: the majority of triggers are polling triggers. With a polling trigger, Zapier will check for new data from your trigger every 1 to 15 minutes in order to start your Zap, depending on your pricing plan.
  2. Instant trigger: with an instant trigger, your trigger app will send Zapier an instant notification whenever there's new data. Zaps with instant triggers are labeled Instant on your dashboard and in the Zap editor.