pipedream
pipedream copied to clipboard
[BUG] Can not create Salesforce Instant sources
Describe the bug First reported by a customer here: https://pipedream-users.slack.com/archives/CPTJYRY5A/p1662346083419929
Hi All - New to Pipedream. Considering adopting it as core part of our integration stack. However, it seems I can't create a Salesforce source for instant updates (I have tried this with a few other tools and works just fine so I don't believe its permissions related). Keep getting "Create webook error"
The customer also reported that he tried this with n8n.io, tray.io, and AWS AppFlow, all work with instant style triggers. I've only had this issue with Pipedream.
To Reproduce Steps to reproduce the behavior:
- Access Pipedream > Source
- Create a new Salesforce - New Object (Instant, of Selectable Type)
- Observe error
UNKNOWN_EXCEPTION: admin operation already in progress
Expected behavior The source is created successfully.
Happy to provide some time to help debug this. Timezone - AEST
Hello @jverce, could I request your help for this issue 🙏 ?
@sweepy84 is evaluating Pipedream Enterprise plan and want to use our Salesforce Instant sources, though he have an issue on his side when creating the source that I couldn’t reproduce.
Upon further checking, I see that our Pipedream instant source is using [salesforce-webhooks
package (https://www.npmjs.com/package/salesforce-webhooks) that you authored, so I think you might be able to help 🙏
I've asked @andrewjschuang to take a look at this. @sweepy84 also said that we fail to list custom objects in the Object Type field of the "Instant" sources. They appear to correctly appear in the list for the Selectable Type components. See https://pipedream-users.slack.com/archives/CPTJYRY5A/p1662596198836909 for more information.
for OLD salesforce New Object (instant , of scaleable type) iam able to create source/trigger successfully
TestCase on this new PR
i was able to create source , SObject type as Product ,Account etc...
but i can’t create source when i select SObject type as AI insight action
@jverce I see what you're saying to filter the correct SObject Types, but in the salesforce-webhooks package, it returns a static list of objects, thus custom objects are not selectable
Hello @dannyroosevelt @andrewjschuang, I'm able to create sources for standard object & custom object, and they work correctly Salesforce_4196_2350.pdf
Though there're 2 cases need your attention
Improvement needed: Initial Historical events are not emitted
When I deployed a new source, there’re no initial historical events when I first deployed the source
Suggestion: I suggest that we release this fix and create another Github issue for improvement. I've created a new Github issue here: https://github.com/PipedreamHQ/pipedream/issues/4264
Bug fix: the source can not be created - Skipped
Per the bug report here: https://github.com/PipedreamHQ/pipedream/issues/4166#issue-1361779075, I can not reproduce the bug. Hence, I could not confirm that it has been fixed.
Suggestion: I suggest that we release this and communicate with the user to test on his side after we released this
What do you think?
@dylburger @vunguyenhung @andrewjschuang - This issue persists for us. Unable to create any instant sources to salesforce. As mentioned in slack this has worked with the same salesforce instance/account with all other service providers I've tried. Happy to jump on a call to help resolve.
Hi @sweepy84, can you please check if there are any triggers configured? If there are, would it be ok to delete them and try again?
Note for reference - It appears that when we try to create an Apex Class or Apex Trigger (2 things Pipedream Salesforce source requires) it fails with the below messages. This appears to be something to do with Salesforce locking. A support ticket was raised. Will provide further updates for reference.

