TIMEOUT on Bitbucket Webhooks

It was HTTP status200, but turned into sudden timeout so far.
I do not come back to HTTP status 200 in a state of timeout afterwards if it becomes timeout.
Generally, in time for update, I am as follows.

Elapsed time: 5178ms

When perform resend request; HTTP status: It becomes 200.

It wants to prevent it from becoming timeout, how is it all right?
The port has been released, and the practice of the file by the trigger is done, too.

I look forward to hearing from you.

0 answers

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

1,936 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you