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
We should run this by the JIL/UMAPI team to make sure we are making the correct assumption to assume the user is active if the status field is not provided.
Do we have a consistent way to reproduce this behavior?
Oh - I didn't notice this was for Sign API (UMAPI has a similar status field). Let's reach out to Sign engineering and confirm the correct behavior here.
Description
Error gets thrown when userStatus isn't present as a key. We need to allow the user to be included if the key is missing.
Steps to reproduce
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
The text was updated successfully, but these errors were encountered: