Troubleshoot Guided Onboarding

Resolve common access, assistant, sample data, mapping, artifact, and scenario issues in Guided Onboarding.

A Guided Onboarding workflow does not behave as expected.

You might not see a scenario tile on the Onboard data page if your deployment does not include the scenario or your role does not have access to it.

  • Verify that you opened the Scenarios page in the correct Splunk Cloud Platform environment.
  • Ask a Splunk administrator to confirm your Guided Onboarding permissions.
  • Ask your administrator to confirm that the scenario is available for your deployment.

You can view scenarios but cannot start a scenario or update task status because your role might include read access but not permission to start scenarios or update task status.

  • Ask a Splunk administrator to grant permission to start scenarios and update task status.
  • Sign out and sign in again after the permission update.

The assistant does not continue after you answer a question because the active question might still require a structured answer, or background processing might still be running.

  • Review the active answer panel for required choices.
  • Wait for the assistant to finish processing before you send another chat message.
  • Refresh the page if the UI does not show the expected update after processing finishes.

Sample data upload fails in the Schematize custom data scenario because the sample file might exceed the upload limit or contain content that the browser cannot preview.

  • Confirm that the sample file is 30 MB or smaller.
  • Use a smaller sample that still includes representative event types.
  • Enter or paste sample events directly if file upload is not available.

Generated mappings, files, or packages include warnings when Guided Onboarding does not have enough representative sample data or a required CIM field does not appear in the sample.

  • Review the validation results and the explanation for mapping decisions.
  • Verify that the sample data includes normal events, error events, and edge cases.
  • Use chat to request supported attribute changes before you download the output.
  • Document any manual changes that you make to downloaded files or packages.