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.
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 ...
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!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot