Resubmitting question to Banno digital support as my question was deleted. I have an automated process that runs several Banno API calls to unenroll a user from the Zelle Ability. The first time I run the below API call to get the User Abilities in Production I receive a 404 error for every new account.
GET (a/mobile/api/v0/institutions/institutionID/users/userID/abilities)
Five minutes later the process runs again (using the same data, same process) to check for new users, sees the failed user and attempts the same API call which is now successful. I have seen this behavior across 15+ unique member accounts. I am unable to replicate the issue in our test system. Is this a known issue with this specific API call?
After reviewing the logs for one of the requests that you shared (via the x-request-id) the most likely cause for this observation is hitting a race condition with new users.
When a new user is created, the user record needs to be hydrated throughout a series of different systems. Sometimes if a user is new, not all systems will have a record of that user just yet, which is why you will see the user in your list of all users, but will receive a 404 from the a/mobile/api/v0/institutions/{institutionID}/users/{userID}/abilities (this endpoint may not know of the user just yet).
This would also explain why you see the 404 first, then successfully make the request a few minutes later.