​@meshfemi are you still experiencing this? when you said it was several users, does that mean that others continued to use MWO and sync without issues? If so, what’s common about the users who had the issue?

This message is likely the result of a network call failing, so were the affected users all connecting via the same connection at the same time, for example?

Best regards,

Rukmal

Many thanks ​@Rukmal Fernando for your reply. Actually, the MWO users who were experiencing the issues are now fine, they can login to the MWO without the error message. 

I’m just curious what could have be causing the error message?

Thanks

Mesh 

​@meshfemi Glad to hear it’s resolved now. This is very likely the result of a network call failing, since MWO queries the TAS initially in the login process, and that appears to have returned an empty response, which I suspect was due to a network issue or the call timing out.

Best regards,

Rukmal

​@Rukmal Fernando , actually below was the findings 

Issue:
Upon investigation, we discovered that the redirect URI for IFS Mobile Work Order (ifs-app.com.ifsworld.mwo10://app) was not configured in the customer's Azure Active Directory (Azure AD). As a result, the application failed to properly redirect as expected.

Resolution:
We have added the correct redirect URI to the customer’s Azure AD setup.