Pipeline speed and workarounds.
I have been testing my pipelines that I have migrated from automations and they run much slower comparatively. A process that took maybe 5 seconds max to do in my automations, now takes 40 seconds to ...
Forum Discussion
My only suggestion is to have something - maybe a form rule set a date time stamp when the pipeline would have been triggered and then the last step of the pipeline can set a time stamp when it completes. Then use those time stamps to provide feedback via an icon or message to let the user know that "you child record are being created... Please refresh ....."
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------
Thanks, I'll consider that.
------------------------------
James Dalton
------------------------------
------------------------------
James Dalton
------------------------------
- James,
Unfortunately I agree, that this is just the way it is. I had planned on using automations for anything I needed completed instantly, and Pipelines for all processes requiring complexity. This was a perfect solution for me, so I was quite disappointed when they announced automatons are going away. I kept hoping that with enough pushback, they would leave automations, but I've lost hope. I have roughly 100 automations I need to switch over to Pipelines, and am not looking forward to it.
------------------------------
Mike Tamoush
------------------------------- Hi Mike,
Yes, it just seems silly to get rid of automations. Can't they co-exist?
QB announced in their Empower talk how they are growing and expanding globally. So you would think they have the resources to support both services.
Weird.
Good luck with your migration. If I stumble on anything useful, I will definitely share it.
------------------------------
James Dalton
------------------------------
