Request timeout

[JAStanton]

Apple is taking longer than 30 seconds to respond to the request to invite a user. These are logs as an example:

2016-10-12T16:22:21.454784+00:00 app[web.1]: Processing by InviteController#submit as HTML
2016-10-12T16:22:21.454896+00:00 app[web.1]:   Parameters: {"utf8"=>"✓", "authenticity_token"=>"XXXX", "first_name"=>"Tyler", "last_name"=>"Blueberry", "email"=>"[email protected]", "commit"=>"Get Beta Access"}
2016-10-12T16:22:21.472417+00:00 app[web.1]: Going to create a new tester: [email protected] - Tyler Blueberry
2016-10-12T16:22:51.461781+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=POST path="/submit" host=XXXX.herokuapp.com request_id=XXXX fwd="XXXX" dyno=web.1 connect=1ms service=30000ms status=503 bytes=0
2016-10-12T16:24:36.768031+00:00 app[web.1]: Existing tester [email protected]
2016-10-12T16:24:36.768047+00:00 app[web.1]: Successfully created tester [email protected]
2016-10-12T16:24:36.943163+00:00 app[web.1]: Addding tester to application
2016-10-12T16:24:37.918718+00:00 app[web.1]: Done
2016-10-12T16:25:13.913895+00:00 app[web.1]:   Rendered invite/index.html.erb within layouts/application (3.0ms)
2016-10-12T16:25:13.922352+00:00 app[web.1]: Completed 200 OK in 172467ms (Views: 14.4ms)

Heroku says this about long lived requests:
https://devcenter.heroku.com/articles/request-timeout

The timeout value is not configurable. If your server requires longer than 30 seconds to complete a given request, we recommend moving that work to a background task or worker to periodically ping your server to see if the processing request has been finished. This pattern frees your web processes up to do more work, and decreases overall application response times.

Note the user IS being added. But the server is just giving a bad response after 30 seconds. Pretty undesirable. The boarding app should be smart enough to deal with long lived requests.

[mhassanpur]

Any updates on this? Seems like it is consistently taking longer than 30 seconds to add a user on my end. Definitely undesirable behavior.

[joshdholtz]

@JAStanton @mhassanpur Is this still an issue for you both? I have not been able to see this error myself