What to look for:
Search for error messages or exceptions that coincide with the time you try to access the “Schedule Tasks” page.
Look for stack traces, which show the sequence of events that led to the error.
Pay close attention to any messages related to:
It’s possible that one or more TaskDefinition objects in IdentityIQ are corrupted or have invalid data. This can disrupt the loading of the “Schedule Tasks” page.
In the IdentityIQ debug pages, try to examine the TaskDefinition objects. Look for any that seem incomplete or have unusual values.
If you identify a corrupted TaskDefinition, you might need to:
Delete it (if it's a custom task and you have a backup).
Restore it from a backup.
Recreate it.
Caching Problems:
Sometimes, stale cached data can interfere with page rendering.
Solution:
Clear the IdentityIQ server's cache.
Clear your browser's cache.
Note: Please compare this section with working environment, try to update if you find any difference. please take backup before any changes to revert back. you play with this UI customization to sort out the column which is causing display in case.
I think the problem is not in the struct of the page or in the library, usually depends on the data that you have.
It could possible into the logs you can find the problem, but you can check, via debug, the TaskSchedule objects. For example:
if you find something similar, it means something gone wrong, so you can try to delete those object(or all) and recreate it.
About ColumnConfig’s properties the most important is property; this is the class or attribute name that you want print or work on it. The properties that you can use depends of the datasource or the object that you are using. In this case you can set every attribute of TaskSchedule object.
if you find any ids under name column when you search with string TaskSchedule delete those records from debug pages. in general, TaskSchedule name should be string values but in the above screenshot name column contains lengthy DB ID reference column, which is treated as bad data, could be deleted.
In general
id and name should be like below in case if you find lengthy DB id reference those could be considered bad data, you can delete them