Debugging 500 Error on Salesforce Trigger?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

I’m getting a 500 error response on the salesforce trigger. Can anyone help me debug this?

Captura de pantalla 2023-04-20 a la(s) 6.09.33 p. m..png
Captura de pantalla 2023-04-20 a la(s) 6.09.33 p. m..png1005×925 59.3 KB

2

can you help triage when you get a chance?

3

Sure! I’m going to triag this now. I’m setting up Salesforce

4

Hello , I couldn’t reproduce your issue as I can create the source okay. In order to investigate further, could you confirm some of the points below?
• You have enabled Salesforce REST API per this document
• You have the permission to:
◦ Creates a Remote Site Setting
◦ Deploys some supporting Apex classes
◦ => I would suggest you to add the admin permission if possible
If you can expand your error (2nd image below), it might have more information

image.png
image.png2766×1528 391 KB

image.png
image.png1005×925 61 KB

5

let me check!

6

I am a salesforce admin, so I believe the correct permissions are set. I can correctly see all of my salesforce objects in Pipedream, I get a slightly different error now. Attaching…

Captura de pantalla 2023-04-20 a la(s) 10.50.11 p. m..png
Captura de pantalla 2023-04-20 a la(s) 10.50.11 p. m..png2110×246 45.8 KB

7

here is the full trigger

Captura de pantalla 2023-04-20 a la(s) 10.51.41 p. m..png
Captura de pantalla 2023-04-20 a la(s) 10.51.41 p. m..png2174×1886 396 KB

8

I tried creating a Source outside of a workflow, and got this error

Captura de pantalla 2023-04-20 a la(s) 10.53.53 p. m..png
Captura de pantalla 2023-04-20 a la(s) 10.53.53 p. m..png2234×1952 492 KB

9

I see, can you expand this Create webhook error part?

Captura de pantalla 2023-04-20 a la(s) 10.53.53 p. m..png
Captura de pantalla 2023-04-20 a la(s) 10.53.53 p. m..png2234×1952 470 KB

10

Captura de pantalla 2023-04-20 a la(s) 10.56.45 p. m..png
Captura de pantalla 2023-04-20 a la(s) 10.56.45 p. m..png2146×1366 434 KB

11

pipedream shows up under “Oauth connected apps” in salesforce so it appears the permissions are correct

Captura de pantalla 2023-04-20 a la(s) 10.57.01 p. m..png
Captura de pantalla 2023-04-20 a la(s) 10.57.01 p. m..png2812×182 23.9 KB

12

your error sounds quite familiar, I’ll ping the component dev who has the context on the matter to check :pray:

Hello @U02S7FH4T89, as you are familiar with Salesforce source, would you mind taking a look at the error?

13

In the mean time as a workaround, would you mind trying to use the source that’s not Instant?

image.png
image.png2148×762 102 KB

14

sure let me try, but I want to trigger this only once rather than polling on an interval.

15

Yeah I understand, I have pinged the component dev regarding your issue of the instant source. Until he triage it, the workaround for you to have the feature available now is use the polling source instead. After the instant source is working for you, you can simply switch your workflow to use the instant source

16

Yes the non instant one seems to work. I’ll use that one for now. Thanks!

17

@U03CXTHK4RF is there a github issue I can follow to track the resolution of this so I know when I can start using the Instant Triggers? The polling triggers won’t really work for us in production.

18

Yep ! Thanks for your patience, here’s the link to the issue. I’ll start working on it ASAP

19

you the man!

20

Hey ! I was able to create a webhook normally.
Can you please follow these steps and try to create the instant trigger again?