How to Prevent "New Row" Trigger in Google Sheets from Invoking Without a New Row?

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

Hey there,

I just noticed that the “New Row” trigger for Google Sheets triggers new invocations even though there’s no new row on Google Sheets.

Is there a way to prevent this? I think it should count as an invocation only when a new row is present.

And the weird thing is that the invocations are seen as New Updates (Shared Drives, Instant) and just “New Updates”.

Why is this happening?

Hello , the Google Sheet New Row source will emit event even for empty row. I suspect this might be the case. May I ask if you added any empty row to your sheet?

Loop in @UR84EMEUT as you have context on this

Hello . “New Row Added (Instant)” and “New Updates (Shared Drive, Instant)” are two different Google Sheets triggers. It looks like you might have both of them running? Are they both listed in your Sources tab?

there’s only “New Row Added (Instant)” triggers, but somehow the triggers look like duplicates. I don’t use “New Updates (Shared Drive, Instant)” anywhere. You can see that the number of invocations are exactly the same.

I think there’s a bug there, and I deserve a refund for the extra payment I’ll be making this month.

Hi , I’m so sorry for your issue. In order for Pipedream team to investigate more on this, could you ping @U02SX7ETBFB from Pipedream team or send an email to support@pipedream.com stating your issue again? You should get the response in a few hour when Pipedream support is back online

I believe Pipedream team will definitely eager to support your issue

, No, I’m not adding any empty rows. There’s a pivot table that checks the valid rows on another sheet, though. But I think it’s unrelated to that because there are too many triggers.

For example, there was only one event that happened but the logs show invocations almost every minute.

I needed to pause all the workflows that triggers with Google Sheets.

I see, Thank you for more information . Maybe @U02SX7ETBFB from Pipedream will be able to explain this charging credit behavior and also support you on your billing.

Again, I’m sorry for the inconvenience. Could you please wait a few hours until he comes online?

Hi Cagri, in our old billing system all source executions cost an invocation regardless if an event was emitted or not.

In the new workspace model, you’re only charged if the source runs for more than 30 seconds (aka the first credit is free).

We’re still in the process of migrating older accounts to this new model. Do you have a subscription with us? If so, what kind is it?

can you explain how sources credits are incurred differently from workflows?

Hi , I’m currently using the old Professional Plan because it’s more affordable and has more features than the new Basic plan.

Got it, thanks for confirming that. Yes that source invocation behavior is the case with Professional & Teams plans. But you should have received an email from us about the upcoming migration, and by default you’ll be given free source credits to help with this problem. You should see a huge decrease in credit usage when your account is migrated to a workspace.

I see, thanks for that . I’ll check the email.