Re-discovery errors

Edit online

If a re-discovery job fails, you can identify the cause by reviewing the system logs and status details. Common issues often involve authentication failures that prevent Concert from accessing the cluster.

Go to the Administration > Event log.
Locate the failed discovery event and click the Event ID to view details.
Common errors, such as Invalid or expired credentials will be listed in the event status details.

Once the connection is restored or the environment configuration is corrected, manually trigger the discovery job again by using the Run now option.

Updating credentials for re-discovery

If your re-discovery job fails due to expired credentials, complete the following steps:

Go to the Administration > Integrations, select the Connections tab.
Locate the connection associated with your discovery job.
Click the overflow menu and select Rotate credentials.
Enter the new token or updated authentication details, and click Save.
Return to the Ingestion jobs tab and select Run now to restart the discovery process.