Skip to main content
Question

Workaround for 90 Pipeline Limit?

  • Apr 10, 2026 12:01 AM UTC
  • 4 replies
  • 325 views

Forum|alt.badge.img+1

I have reached 90 Pipeline (triggers) limit for my table.

I need to do more pipelines with that table, anyone has a workaround ? (I cannot turn off pipelines)

Here's what I've tried so far:

1- Zapier/Make : doesn't work because I cannot trigger a zap if a specific field was updated. 

2- Consolidate pipelines: Doesn't work because I cannot set a condition of "what trigger caused this pipeline to fire)

3- Look up field in another table and trigger the field based on that: Doesn't work, QB doesn't trigger workflows on lookup fields

4-  (3) + A formula field that dynamically sets the value matching the field on the main table: Doesn't work, QB doesn't trigger workflows on formula fields

 

 

4 replies

MarkShnierYou
Forum|alt.badge.img+24
  • Qrew Champion
  • Apr 10, 2026 12:13 AM UTC

I suppose if you are desperate enough, you could make a new table called XYZ Pipeline Triggers and use your last (90th) Pipeline to Trigger on any change to any possible trigger field and do a Bulk Upsert to XYZ Pipeline Triggers, Merging on a Custom Key field of [Record ID# of the Real XYZ].  I think that will give you 90 more triggers.  

Just by the way, I recently had occasion to make 18 pipelines trigger off the same field being changed.  They all triggered and ran simultaneously very quickly with no problem at all. Nothing really to do with your situation other than I was wondering if there is any limits to how many pipelines could be triggered off the same field being edited on a record. 


MarkShnierYou
Forum|alt.badge.img+24

I'm not suggested a connected Sync table (due to th 1 hour delay). I'm suggesting that you use your last remaining pipeline to create or update a small version of your record in other table.

 


Forum|alt.badge.img+9
  • Qrew Member
  • Apr 17, 2026 5:17 AM UTC

Is the suggestion working for you? I would be curious about your various triggers. Perhaps there is another field you could create to help you determine the trigger in order to consolidated some of them.  Perhaps jinja could be utilize more? 


Top Step
Forum|alt.badge.img+12
  • Observing
  • Oct 21, 2026 4:04 PM UTC

On your #2, you can actually tell which field changed. On a Record Updated trigger (or On New Event set to modify), Pipelines gives you the old values with $prev.

So one pipeline can watch all the fields, and each branch checks its own field with a condition like:

{{a.status != a.$prev.status}}

Chain one of those per field, and each branch does what the old single-field pipeline did. That lets you fold a lot of those pipelines into one and free up triggers.

A few things to know. $prev only exists on updates, not adds or deletes. It works in regular Jinja but not inside an Advanced Query string. And if two watched fields change in the same save, both branches run, so test that case.