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
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?
I see what you mean, I would need to think if this causes any race condition (field updating rapidly in a specific moment) I don't think so, but I will try it
I Have a bunch of pipelines that are for "Notifications" which. basically call a webhook (always the same webhook) with a "Notification Template" whenever something gets changed (Survey gets booked, install gets scheduled/cancelled etc) I could think ok making a "Current Notification" field...
I just realized while writing this, that formula fields wont trigger pipelines either
My suggestion for the formula fields would be to use them in a condition step(s) to determine what path of logic to follow, and/or use Jinja to determine what to do and when. You may be able to take that approach to help you consolidate a couple of pipelines here and there. For example, I populate a rich text field for my notifications and build out my message based on values of other fields (some are formula checkboxes but others are based on particular field values) using Jinja. If fieldA then <message> else "", if fieldB then <message> else if fieldC then <message> else "", and so on. You could try something along these lines to reduce your pipeline footprint. Especially if different triggers currently follow similar enough paths of logic.
