Why does the first attempt to deploy triggers in Salesforce always time out, the second one succeeds, but fails to activate upon testing and where can I view triggers for external users in the dashboard?

Help
61

deployment only works from the second retry, on the first the PD api always times out
You’re making two deploy requests because the first one fails and the second one succeeds?

62

yup

63

i don’t understand how to make pipedream forward the data to my webhook url
The webhook_url param should be outside of the configured_props

64

And it’s just a string, not a list

65

See the docs here: Deploy trigger - Pipedream

66

The timeout issue might be related to a cold start + the API calls the trigger makes when deploying, but I’m not sure

67

What’s the response you get when it times out?

68
  1. thanks for the doc, i was looking at some other method i think and confused the 2
  2. for the timeout i just get a generic:
{
  "rawResponse": {
    "headers": {},
    "redirected": false,
    "status": 0,
    "statusText": "Unknown Error",
    "type": "error",
    "url": ""
  }
}
69

okay, interesting, i tried a deploy again and didn’t get a timeout this time

70

so maybe this was some temporary issue that already got resolved

71

Yeah strange

72

But it could still be what I was thinking above

73

the cold start?

74

Yeah

75

could be, but but that’s weird, the cold start should not take long enough to time out the request, it was like a 60 or so second timeout

76

I don’t think cold starts are an issue for trigger deploys, since it’s the first time we’re deploying the lambda. It’s not it’s deployed and waiting to be executed but has gone cold, we haven’t deployed it yet.

77

Oh it’s 60 seconds timeout?

78

Yeah I was saying the cold start + the API requests to Salesforce

79

Well it wouldn’t be a cold start is my point

80

didn’t time it at the time, but it felt very long so around 60 i would say