Cloud Code timeout in parse-server

[jasonm1]

Describe your issue in as much detail as possible.

I have a Cloud Code beforeSave that can take longer than 3 seconds to complete. Of course, this was impossible on the Parse hosted service, as it had a 3 second timeout, but I don't see why that needs to be the case on parse-server. Can I extend the timeout, and if so, how?

Environment Setup

• Server

  • parse-server version (Be specific! Don't say 'latest'.) : 2.2.2
  • Operating System: Amazon Linux 2016.09
  • Hardware: AWS
  • Localhost or remote server? AWS

• Database

  • MongoDB version: 3.0.11
  • Storage engine: MMAPv1
  • Hardware: ObjectRocket
  • Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): ObjectRocket

Logs/Trace

You can turn on additional logging by configuring VERBOSE=1 in your environment.

[Error]: The request timed out. (Code: 100, Version: 1.14.2)

[ethandrower]

hmm is the response code important to your app? You could use the trigger to kickoff a cloud job I'd think which doesn't have a timeout

[flovilmart]

There is no timeout enforced by parse-server, the only timeout you'll hit will probably be from the http server configuration.

[joaoarmando]

Hello @flovilmart, I'm having this same problem, can you explain me how to increase the timeout time on the http server you mentioned?

[JacobJT]

@joaoarmandoo This forum is for issues with the SDK itself, rather than your implementation, so it's not an appropriate place to get that kind of help. Try stack exchange. And for a little direction, the http server is actually nothing to do with parse-sever itself. Parse-Server gets mounted to your http server, it's something totally separate, and every one of us could have something entirely different. For example, I deployed parse-server on AWS using Elastic Beanstalk, and my EC2 Instances I run it on use ngrok as the http server. So, when I needed to update my server configurations, it came down to learning how to modify ngrok, totally different.

So, post your set up on stackexchange and someone might be able to help you there.