Duplicate
Details
Assignee
Mykola MakhinMykola MakhinReporter
Mykola MakhinMykola MakhinPriority
P3Story Points
0.5Sprint
NoneDevelopment Team
EurekaTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Mykola Makhin
Mykola MakhinReporter
Mykola Makhin
Mykola MakhinPriority
Story Points
0.5
Sprint
None
Development Team
Eureka
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created October 4, 2024 at 1:34 PM
Updated October 14, 2024 at 3:48 PM
Resolved October 4, 2024 at 2:04 PM
There was a retry mechanism introduced in scope of fo calls made to Kong, Keycloak and FOLIO modules during the entitlement flow.
In case retries are occurring there should be corresponding logging and/or information about retries stored in flow info - right now there are no logs and no info about retries in flow information in DB.
AC:
Make sure there are logs in case of retries
If possible, add retry information to flow information that is stored in DB and can be retrieved via mgr-tenant-entitle API