This message was deleted.
# cloud
s
This message was deleted.
d
👋 Neil, what are you guys seeing?
e
Hi David,
We've been developing against our own deployment on AWS.
We just switched to a dev account on cloud to start testing
But we are seeing much slower responses to API calls, which on our end has caused a couple of race conditions
But now I am trying to start a recording and just getting a 500 back from the egress
This on
relayeddev
on my account
d
Some APIs will respond slower due to it being globally distributed. There's a bit of synchronization that happens to ensure API responses are accurate. Re Egress failures, can you send me the request that you've used?
e
Yeah sure, I'll paste here the main command that returns the 500 if thats cool
👍 1
ooohhh hmm just realised what might be causing the issue - in our setup the S3 was defined in the deployment of the egress servers
➕ 1
I'll need to pass that to yours in the call
d
ah yeah! that would make sense
e
Also am I able to point to our own custom templates (egress)
🙌 1
d
we'll be making that easier over time, where you could configure defaults in the project portal
glad to hear it.. our docs there aren't super great.. we'll enhance it
e
can I point to our own custom template for egress on your end?
I don't think the API has that option no?
we set in the egress deployment on our own
@dry-elephant-14928 ^ not sure you saw my last question - thx
okay I see you answered on my other thread - thanks
Is there a big delay in Webhook events and the data being correct in the API requests for participants, etc
seeing quite big delays between what we were testing on our own environment and your cloud
d
Hmm I'm not following what you mean. can you give me a specific example?