-
Type: Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Sprint:2023.R3 Signal Int. Sprint 3
-
SCRUM Team:Globogym Purple Cobras
-
Story Points:3
-
Work Type Classification:Sustaining
Story
As a project admin, I would like to add a retry logic for signal API call failures and improvements in AuditLog records
Description
Retry Implementation
A re try example written in mms services
Dim retryCount As Integer = 3 While Not readonlyFlagUpdated Try UpdateReadOnlyFlag(entityId, localTime, startDate) readonlyFlagUpdated = True Catch ex As Exception retryCount = retryCount - 1 If retryCount < 0 Then AuditService.Audit(BusinessObjects.AuditItem.AuditCategory.Forecast, BusinessObjects.AuditItem.AuditEvent.ForecastReadOnlyFlagUpdated, "Forecast ReadOnlyFlag Not Updated", ex.Message, Convert.ToInt32(entityId)) End If Thread.Sleep(1000) End Try End While
Audit Improvements
We should have a separate logging for each Signal API calls with the URL information is getting called and also duration.
We should be able to understand what call is taking how long so that we can identify if the main issue related to Okta or the API.
AC
- Confirm that there is a retry logic implemented for the Signal API calls failures(Create and Update Transfer) and the error should be logged in case the last attempts fails.
- Confirm that Okta API call has a separate audit log entry with its URL and duration
- Confirm that Create Transfer API call has a separate audit log entry with its URL and duration
- Confirm that Update Transfer API(Receive/Deny) call has separate audit log entries with its URL and duration
- blocks
-
CFAMX-24355 Signal - Remote API fails the First Time it is Hit
- Done
There are no Sub-Tasks for this issue.