Hi Geoffrey, Thanks for letting us know about the errors you're seeing. I'm not able to reproduce them using the same requests as before; i.e. posting more than one CCR type (e.g. Medications and Conditions) in the same request to the H9 register feed. Are you also posting to the H9 register feed? What authentication scheme are you using (AuthSub, OAuth, or ClientLogin)? Thanks in advance for any additional information you can share!
Paul (Google) On Jul 28, 6:11 pm, Geoffrey <[email protected]> wrote: > Hello all: > > This issue may be occurring again. I have seen both 500 Internal > Server Error and 502 Bad Gateway in response to posts. > > Thanks, > > Geoffrey Roberts > Private Access, Inc. > > On Jul 14, 5:38 pm, "Paul (Google)" <[email protected]> wrote: > > > > > Hello All, > > > The issue has once more been resolved, and we're looking further into > > what might be causing it to occur. We will continue to post updates > > in this thread. > > > Thank you all for your reports, and especially your patience. Both > > are greatly appreciated! > > > Paul > > > On Jul 14, 2:45 pm, SBME 2010 <[email protected]> wrote: > > > > The same problem appears again :(((((((((((( plz Pual try to fix this > > > problem completly bec. we will have a presentation about our application > > > that is related to H9 sooooooon > > > > Thanks so much > > > > On Tue, Jul 13, 2010 at 3:08 AM, Paul (Google) <[email protected]> wrote: > > > > Hi All, > > > > > This issue is currently resolved; although, we're continuing our > > > > investigation of the root cause. Please don't hesitate to post a > > > > message in the forum if you experience additional difficulties. > > > > > Cheers! > > > > Paul > > > > > On Jul 12, 12:13 pm, "Paul (Google)" <[email protected]> wrote: > > > > > Hello All, > > > > > > There is currently an issue on H9 that causes an HTTP 500 response to > > > > > be returned when multiple CCR sections (e.g. Results and Medications) > > > > > are posted in a single CCR document. The issue does not affect > > > > > production Health. We are currently investigating the cause and will > > > > > address it as quickly as possible. Updates will be posted once they > > > > > are available. > > > > > > Thanks to everyone that sent notices of the issue! > > > > > > Kind regards, > > > > > Paul (Google) > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups > > > > "Google Health Developers" group. > > > > To post to this group, send email to > > > > [email protected]. > > > > To unsubscribe from this group, send email to > > > > [email protected]<googlehealthdevelopers% > > > > [email protected]> > > > > . > > > > For more options, visit this group at > > > >http://groups.google.com/group/googlehealthdevelopers?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Health Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/googlehealthdevelopers?hl=en.
