Thanks, I realise that is the case but, as I say, when you are presenting a demonstration or testing multiple times, then the 3 minutes can mount up. Not a big issue when live but worse off when testing/demonstrating
Zaps marked as INSTANT do not have the Run option as those most often use webhooks to send notifications of events, vs non-Instant triggers that use polling on cron jobs (set schedules).
Learn more about the trigger difference here: https://zapier.com/help/create/basics/set-up-your-zap-trigger
Do you have an example of an app’s trigger?
The new and updated spreadsheet row triggers for Google Sheets are unique in that when there is a trigger event in the spreadsheet, Zapier gets a notification webhook from the Google about this following that notification, Zapier sends Google Sheet a request asking for new data. After this, the trigger works using the normal polling mechanism and these new or updated rows returned will trigger the Zap. This process takes about 3 minutes overall so although the Google Sheets trigger is marked "instant" it really is a hybrid of both webhook and polling techniques. While being slower than any other "instant" trigger, it's still faster than all polling triggers which would take 5 or 15 minutes.