Troubleshooting Metadata Campaign Issues

Use this information to troubleshoot common metadata campaign and metadata review issues.

Metadata Campaign Issues

Issue	Cause and Solution
Unable to find a campaign in the Campaigns list	A campaign may not appear in the Campaigns list for one or more of the following reasons: The campaign is completed. Check the Campaigns Completed tab. The campaign is outside your assigned scope. Campaigns outside your scope are hidden. The campaign schedule has not run yet. A filter is applied and is hiding the campaign.
The schedule’s last run result is Success, but the campaign does not appear in the Campaigns tab	This can happen when IdentityIQ cannot create a valid campaign from the schedule configuration. Possible causes include: No primary reviewer could be determined. Review the Choose Reviewer configuration. The object selection criteria such as filters, a rule, or Exclude attributes option returned no objects. Correct the selection criteria. If you use a rule, confirm that it returns objects and that the remaining filters still include them. If you exclude recently validated attributes, update the duration or turn the option off.
The schedule’s last run result is Failed, and the campaign does not appear in the Campaigns tab	This can happen for one or more of the following reasons: The campaign owner could not be found. The owner identity was deleted or renamed. Edit the configuration and select a current identity. The campaign configuration could not be resolved. The definition was deleted or renamed after the schedule was created. Recreate the schedule. The required background task definition (MetadataValidation Manager) is missing. This indicates an incomplete upgrade or import. Contact support. To diagnose the failure, refer to Troubleshooting a Failed Campaign.
The schedule’s last run result is Failed, and the campaign status is Error	Campaign generation may have failed while IdentityIQ was creating review sets, work items, or notifications. To diagnose the failure, refer to Troubleshooting a Failed Campaign.
The schedule’s last run result is Failed, and the campaign status remains Pending	If Enable Partitioning is turned on and a partition does not finish, the campaign can remain in the Pending state while the schedule result shows Failed. On the Campaign Schedules tab, select > View Last Result for the failed campaign schedule. Review the status of the partitions and note the host associated with any Pending partitions. Confirm that the Request service is processing requests on that host. For more information, refer to Using the Administrator Console. After the Request service is processing requests, schedule the campaign again. Alternatively, turn off the Enable Partitioning option and schedule the campaign again on a single thread. For more information about partitioning, refer to Partitioning.
Campaign generated with the Warning status	Generation completed but not everything succeeded. The individual warnings are not currently listed on the schedule result page. To identify what was skipped: Review the task result for the campaign run. Compare the campaign item count against the number of objects you expected to be in scope.
Unable to schedule a campaign	The campaign is scheduled using a background task based on the MetadataValidation Manager object of type TaskDefinition. If this object is missing from the installation, the campaign is not scheduled. Contact SailPoint Support.
The schedule result page shows "No result" for a schedule that has run	The page shows the same empty state whether the schedule has never run or when the result could not be retrieved. To troubleshoot: Reload the page. If the result is still empty, confirm that the schedule has run by checking the task results. Ask your administrator to review the server log.
The campaign contains fewer objects than expected	The Exclude attributes option may be filtering objects out. Adjust the duration or turn off the option.
All reviews are signed off, but the campaign is still active	The campaign moves to Campaigns Completed after a Perform Maintenance (System Maintenance) task run and only if Finish metadata validation sets is enabled in that task options.

Metadata Review Issues

Issue	Cause and Solution
A review is present, but nobody can act on it	When a review is created without a resolvable primary reviewer, the review is kept but its review work item is skipped. Review the Choose Reviewer configuration.
Unable to see a bulk action	Bulk actions are configured per campaign. If a bulk action is not enabled for a campaign, the option is not displayed.
Unable to save changes after a bulk validate or clear	Some items in the batch may not have been updated because they were reassigned or modified while the action was running. Reload the page to see which items were updated, and then repeat the action on the remaining items. Your selection is preserved so you do not lose the batch.
Sign-off fails	Sign-off can fail for one or more of the following reasons: The review was signed off by another user in the meantime. The review work item could not be closed. A connectivity or server error occurred. To resolve the issue: Reload the page. If the review now shows as signed off, no further action is needed. If the review is not signed off, try signing off again. If sign-off continues to fail, ask your administrator to review the server log. The log records the specific reason for the failure.
Attribute changes are not reflected on the objects	Sign-off and write-back are separate transactions. The review set is marked as signed immediately, and a Perform Maintenance (System Maintenance) task run applies the changes to the objects afterward.

Troubleshooting a Failed Campaign

To troubleshoot a failed campaign:

1. On the Campaign Schedules tab, select > View Last Result for the schedule whose result is Failed.
2. Review the error list to know the specific cause behind the failure.
3. If the Partitioned Results table is shown, find the partition that did not complete and check the status of that host.
4. If there is no error list, note the host name and check that server’s log.
5. Fix the issue and schedule the campaign again.