You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
During invocation of Avni External Subject GET API, with Concept filter, receiving error that concept name doesnot exist, even though it does.
2024-11-14 13:03:30,463 ERROR SpringTaskScheduler-3 [avni.client.AvniHttpClient] URI: https://app.avniproject.org/api/subjects?lastModifiedDateTime=2024-10-18T07:02:14.151Z&size=10&concepts=%7B%22Account%20name%22:%22Goonj%20Kerala%22%7D&subjectType=Activity, Errored Request body: null
2024-11-14 13:03:30,464 ERROR SpringTaskScheduler-3 [goonj.job.AvniGoonjAdhocJob] Failed adhoc processActivity
org.springframework.web.client.HttpClientErrorException$BadRequest: 400 : "org.avni.server.util.BadRequestError: Bad Request: One of the specified concept(Account name) does not exist<LF> at org.avni.server.service.ConceptService.readConceptsFromJsonObject(ConceptService.java:361)
Expected behavior
Subject API should return successful response with results that match input concept and other filter values criteria.
Additional details
Impact is not too much for Goonj integration as of now.
LAHI integration used Concept filter based Subjects GET, but isn't active right now
Developer Checklist
Developer fixing the bug should fill this checklist.
Does the fix require extensive regression testing?
Are you mentioning the required scenarios that could be affected?
The text was updated successfully, but these errors were encountered:
Describe the bug
During invocation of Avni External Subject GET API, with Concept filter, receiving error that concept name doesnot exist, even though it does.
Expected behavior
Subject API should return successful response with results that match input concept and other filter values criteria.
Additional details
Developer Checklist
Developer fixing the bug should fill this checklist.
The text was updated successfully, but these errors were encountered: