Why Does the First Request Time Out and the Trigger Not Work When Deploying Triggers on Pipedream?

Help
81

Gotcha

82

Trigger deploys do inherently take a while, a lot of that is dependent no the packages we’re installing for the component source, etc

83

So deploy + API requests then

84

well this seems to be fine now, so idk, something for your tech team to maybe have a look at some point, but nothing urgent. I saw another message about deployment timeouts recently in so maybe this is somehow related

85

It’s probably not related but definitely good to know

86

as for webhooks, i changed the payload to

const deploymentPayload = {
          id,
          externalUserId: session.activeOrganizationId!,
          webhook_url: webhookUrl,
          configuredProps: {
            ...configuredProps,
            timer: {
              intervalSeconds: 90,
            },
            salesforce: {
              authProvisionId: integrationConnection.connectionId,
            },
          },
        };

but the data is not forwarded :disappointed: maybe this only works for instant webhooks and not timer-based triggers?

87

It should work for both

88

dc_4OuMEGZ

89

Oh might be webhookUrl

90

Given the other ones are camel case

91

ahh, maybe sdk v2 thing, you moved a bunch of things to camelCase

92

let me try

93

yup that’s it

94

amazing, let’s end at that, thanks a tone for your help and patience, i’ll try to figure out the SF thing with the salesforce branch of my company on monday, maybe they will able to help me in some way

95

Claude says this, but i highly doubt that’s the reason

image.png
image.png1436×572 71.3 KB

96

Yeah np, glad to help

97

If the Apex code was successfully submitted to Salesforce, maybe you can test it there

98

it seems like it’s failing at the deployment stage

99

If your Apex code is failing in the deployment stage in Salesforce, it means the code passed saving and compilation in your development org (or sandbox), but when Salesforce tries to move it to the target environment (like production), one or more of the deployment validation checks fail.

100

Hmmmmm could this be that the pd env is prod and sf env is sandbox…