We have a Flow that sends data from a 3rd party system into our Salesforce org. Part of this Flow is that a Contact is added to a Campaign.
We recently needed to change the Campaign, however when going into the Salesforce ‘Add Contact to Campaign’ node it freezes, then eventually I get the Page Unresponsive message (below), leading to the Aw Snap message.
Initially, I thought it was due to the complexity of the Flow (there are approx 60 nodes), so before I started to review how to make it less resource heavy (sub flows, reduce code nodes etc), I wanted to double check it wasn’t anything else.
I have since created a 2 node Flow, with a manual trigger and the Salesforce ‘Add Contact to Campaign’ node… and I get the same issue. What else could be causing this? I have asked my colleagues about the self-hosting and they assure me it is running fine in the background (Docker)
Please note the warning/exclamation sign is there as the node is incomplete. Every time I try to add the Contact Id and Campaign details it crashes, and I cannot then share it here
Thanks for posting here and welcome to the community!
Are you just opening the node or also selecting any parameter? Do you have a lot of campaigns to select from? (Could be why this is taking a while to fetch the campaign lists for the drop down)
Do you see anything in your browser dev tool logs?
This is when clicking on the Campaign Name or ID box. We haven’t increased the number of campaigns in our Org and this worked fine before. We do have a fair few campaigns in there - not sure what number equates to too many though.
Would it be quicker/easier just to create an HTTP POST call and do it that way, rather than relying on the Salesforce specific node? It is a good node which our non-technical team could administrate easily, but if its susceptible to crashing on large numbers of campaigns it may be best to move away from using it.
Dev tools showed a websocket connection failure message, if that helps?
the websocket connection failure sounds like a potential culprit in this… Are you using a proxy?
Can you check your server logs for more details related to this? Could be that there is more to fetch now and it may timeout for some reason
You were spot-on (apologies for the delay in confirming the answer). We have a large amount of active Campaigns in our Org and it was timing out.
Short-term I used an HTTP node to create the Campaign Member, rather than putting all the stress on the Salesforce node to go and search through all of our campaigns first.
In the mean time our IT team are updating the server so it doesn’t timeout in the future.
Thank you!
