Studio Troubleshooting Best Practices

There are some common issues that may come up on a regular basis, and this article describes them and how to address them when you find this to be true on your system.

Consumers are Missing Users from the Roster Data

• Best Practices:
  • Check the Job History Logs for any errors and address each as needed.
  • If the jobs logs show no errors, check the staging table for the Provider application in Data Explorer to ensure they have provided the data expected by the Consumer. If they have, then check the Mapping Job Logs to ensure they have processed the data correctly. If they haven't, you'll need to verify that the data is being mapped correctly in the ID Hub.
  • If the Consumer is a .CSV Consumer, check the .csv files to ensure that the data is missing. If it is not, check the ID Hub for mapping configuration.
  • If the Consumer is a REST API Consumer, check the API. By placing the Record Key of the user in question that's found in Data Explorer to find a missing user at the end of the user endpoint, RapidIdentity Studio will return data.

General Studio Best Practices

• If a Provider Job fails, check the Job History Logs for any errors and address each as needed.
• If a Consumer Job fails, check the Job History Logs for any errors and address each as needed.

Other situations will be added as they come about. Leave us feedback if you don't find your common issue here, and we'll get that added as well!