Zoho Sheet New Rows Trigger Firing Twice – creating Duplicate workflow

Status: Awaiting reply · Asked by Graham Saunders-Griffiths on · 0 views

Graham Saunders-Griffiths — Question ·

We are experiencing an issue with one of our Pabbly Connect workflows where the Zoho Sheet – New Rows trigger is firing twice for the same newly created row, causing duplicate sales orders to be generated in Zoho Books.


Affected workflow:
2024 RX NXT+AF+Thinning - Sales Orders in Books


Details of the issue:

We have four separate workflows monitoring the same Zoho Sheet workbook and worksheet:

  • Workbook: 2024 RX ORDER MASTER SHEET

  • Worksheet: RX Orders

  • Trigger: Zoho Sheet → New Rows (Instant)

Three of these workflows operate correctly, triggering only once per new row. However, the workflow identified above consistently triggers twice for a single newly created row.

We have conducted several tests and confirmed the following:


  2. • Only one row is created in Zoho Sheet.

  3. • Two separate executions are recorded in Pabbly Task History for the same row (see two task history IDs below)

  4. • Both executions receive identical row data and have the same trigger timestamp.

  5. • The two executions have different Webhook IDs.


  7. We migrated the workflow from the Classic Builder to the New Builder, but the problem persists. We also refreshed the trigger fields and saved the configuration again, without resolving the issue.


Example from our latest test (7 November 2026):

  • Zoho Sheet row index: 553

  • Row type: NEW

  • Trigger timestamp: 13:58:25 (Taipei time)

  • Both workflow executions: 13:59:05

  • Webhook ID 1: 6514267000007696000

  • Webhook ID 2: 6514267000007450000

The two executions are occurring simultaneously, resulting in duplicate sales-order creation attempts.


Could you please investigate whether this workflow has duplicate webhook subscriptions or event registrations associated with the Zoho Sheet trigger?


We would appreciate it if your technical team could identify and resolve the underlying issue, rather than requiring us to introduce additional filtering or duplicate-prevention steps.


We can provide screenshots of both task executions and their trigger responses if required.


Thank you for your assistance.


Graham

Back to all forum threads · Log in to reply