Workaround for 90 Pipeline Limit?
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- Zap...
Forum Discussion
MarkShnier__You
Qrew Legend
Qrew LegendI 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.
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)