search

HRHR-project / e-registry-app

0 stars 1 forks source link

Management save failed error #119

Open AkubaD opened 5 years ago

AkubaD commented 5 years ago

We see this error on Bangladesh production but have not yet been able to replicate on dev. The production instance eReg version was updated to match dev, but the error persists.

Screenshot 2019-03-25 at 09 56 21
lukasewvd-zz commented 5 years ago

Hi @AkubaD, are you able to consistently reproduce this issue on dev? If so would it be possible for you to click on of the errors seen in the bottom and copy the data/message in the "response" tab?

AkubaD commented 5 years ago

Hi @lukasewvd . No, as I mentioned above, this has only been seen on production. We have not yet been able to replicate on dev. @RahmanMonjur could you provide the information Lukas is requesting: click on the errors and paste the message here and/send a screenshot? Thanks

lukasewvd-zz commented 5 years ago

Hi @AkubaD. Yes sorry, I meant prod. Are you able to reproduce it there consistently?

AkubaD commented 5 years ago

@RahmanMonjur has been able to see it at least twice - before and after the eReg app update.

lukasewvd-zz commented 5 years ago

@AkubaD okay thanks. It would be great if we could get the message from the "response" tab to get a clue to what is going on.

AkubaD commented 5 years ago

Hi @lukasewvd . We are in a meeting wtih BAngladesh right now. I will follow up with @RahmanMonjur about this once we are done at 11:30. Thanks

RahmanMonjur commented 5 years ago

Hi @lukasewvd, its saying "{"httpStatus":"Conflict","httpStatusCode":409,"status":"ERROR","message":"At least one of the following query parameters are required: orgUnit, program, trackedEntityInstance or event."}"

AkubaD commented 5 years ago

thanks @RahmanMonjur . It looks like the managements save for some management conditions - in the screenshot there is a saved management for Low weight. Is that the case? That it is not all managements that are not saving? In that case, @lukasewvd, do you think it could be related to program rules?

lukasewvd-zz commented 5 years ago

I am not sure about the root cause yet. The server is complaining about a missing parameter. @RahmanMonjur could you on a failing request (like the one you checked the "response" tab for) go to "Headers" tab and scroll all the way to the bottom to the "Request payload" section, click "view source" and copy the data. This might give us an indication of what parameters might be missing.

RahmanMonjur commented 5 years ago
Screenshot 2019-03-27 at 19 18 33 Screenshot 2019-03-27 at 19 18 19
AkubaD commented 5 years ago

Hi @lukasewvd and @RahmanMonjur Do you have an update on this?