Workaround for 90 Pipeline Limit?

Question

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

markshnier__you · Answer

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].&nbsp; I think that will give you 90 more triggers.&nbsp;&nbsp;Just by the way, I recently had occasion to make 18 pipelines trigger off the same field being changed.&nbsp; 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.&nbsp;

markshnier__you · Answer

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.&nbsp;

odeykassam · Answer

Thank you for the suggestion!I thought about that but wouldn't that require me to have XYZ Syncing in real time with my main table? meaning if any record gets created in my main table, also create it in XYZ ? if so, I tried making a table from "source = quickbase" which achieves exactly that, the only issue, is that it's not real time, (1 hour delay)&nbsp;

odeykassam · Answer

Thank you, will try this solution

jamescarr · Answer

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.&nbsp; Perhaps jinja could be utilize more?&nbsp;

Forum Discussion

Workaround for 90 Pipeline Limit?

Related Content

Bulk upsert field limit in pipeline

Qrew Tip: Pipeline Null Values

QrewTip: AI Actions Pipelines Channel

Calculation/Performance Limits Inquiry

Pipeline Help