Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Querying applicants endpoint with name search parameter times out. #11136

Open
designreact opened this issue May 13, 2024 · 4 comments
Open

Querying applicants endpoint with name search parameter times out. #11136

designreact opened this issue May 13, 2024 · 4 comments
Assignees
Labels
2 2 story points added-late An issue that was added to sprint after it began back-end Relates to back end issues bug Something isn't working

Comments

@designreact
Copy link

designreact commented May 13, 2024

Hi Reapit Team 😃

We're still seeing timeouts on the Reapit API for applicant name searches. See our previous issue GET applicants endpoint not returning entities when passing in name parameter #8195.

To Reproduce

The below curl should yield results:

curl -X 'GET' \
  'https://platform.reapit.cloud/applicants/?name=Giles%20Kennedy' \
  -H 'accept: application/json' \
  -H 'api-version: 2020-01-31' \
  -H 'Authorization: Bearer [token]'

Expected behaviour
Response should contain applicant entities.

Actual:

{"message": "Endpoint request timed out"}

Specification

  • Project: Reapit.Services.Applicants
  • Update the full text search mechanism to utilise the updated version from the Reapit.Services.Contacts project (this checks the customers configuration so search behaviour shares parity with the CRM itself, rather than us doing our own thing)
@designreact designreact added bug Something isn't working needs-triage labels May 13, 2024
Copy link
Contributor

Thank you for taking the time to report a bug. We prioritise bugs depending on the severity and implications, so please ensure that you have provided as much information as possible. If you haven’t already, it really helps us to investigate the bug you have reported if you provide ‘Steps to Replicate’ and any associated screenshots.
Please ensure any personal information from the production database is obscured when submitting screenshots.
This issue will be reviewed in our weekly refinement sessions and assigned to a specific project board. We may also update the ticket to request additional information, if required.
For more information on our processes, please click here

@plittlewood-rpt plittlewood-rpt added back-end Relates to back end issues 2 2 story points and removed needs-triage labels May 13, 2024
@plittlewood-rpt plittlewood-rpt added this to To review in Platform Backlog via automation May 13, 2024
@plittlewood-rpt plittlewood-rpt added the refinement To be included in a future refinement session label May 13, 2024
@plittlewood-rpt
Copy link
Contributor

Hi @designreact I've had a quick look at this and can see what this probably boils down to. I'll try get someone onto it soon for you.

@plittlewood-rpt plittlewood-rpt added this to To do in Platform sprint 119 via automation May 13, 2024
@plittlewood-rpt plittlewood-rpt added added-late An issue that was added to sprint after it began and removed refinement To be included in a future refinement session labels May 13, 2024
@plittlewood-rpt plittlewood-rpt removed this from To review in Platform Backlog May 13, 2024
@plittlewood-rpt plittlewood-rpt moved this from To do to In progress in Platform sprint 119 May 13, 2024
@designreact
Copy link
Author

designreact commented May 13, 2024

OK Great, Thanks @plittlewood-rpt 👍

@plittlewood-rpt plittlewood-rpt moved this from In progress to In review in Platform sprint 119 May 16, 2024
@plittlewood-rpt plittlewood-rpt moved this from In review to QA in Platform sprint 119 May 17, 2024
@plittlewood-rpt
Copy link
Contributor

Hi @designreact an update has just gone out which should address this. We'll keep an eye on our logs as we should see a marked improvement in API latency for this endpoint when using name search parameters, but if you could run your own tests and confirm back that it's resolved your specific problem that would be great. Thnaks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 2 story points added-late An issue that was added to sprint after it began back-end Relates to back end issues bug Something isn't working
Projects
No open projects
Development

No branches or pull requests

3 participants