Cloned Agentic Workflow Fails to Predict Fields — Now Assist Skill Config Applicability Not Aligned to Cloned Workflow Use Case NameIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } After cloning an OOB Agentic Workflow (e.g., Predict Service and Transfer HR Cases), the cloned workflow fails to predict fields for a record. The AI agent returns an error such as:[Predict fields for a record or config]: Error while predicting fields for a record: Cannot read property "variable_sets" from undefinedThe OOB workflow works as expected, but the cloned workflow does not. Symptoms<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } - The cloned agentic workflow fails at the field prediction step.- The execution plan shows the prediction step returning an error or empty result.- The workflow appears to complete successfully but the expected field value is not predicted or populated — for example, the HR Service field remains empty after the workflow runs, even though prediction is expected to fill it.- Admins can reproduce the failure in the AI Agent Studio playground.- The OOB workflow (pre-clone) works correctly when tested separately.- No custom scripts or ACL changes are involved. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All versions Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Two options are available depending on whether the customer wants to reuse an existing skill config or create a dedicated one for the cloned workflow.---OPTION 1 — Update the Existing Skill Config Applicability Record (Recommended for single-workflow use cases)Use this option if only one workflow will use this skill config at a time, or if the OOB workflow is not actively in use.Steps:1. Navigate to Now Assist > Administration > Skill Configs (or go directly to sn_nowassist_skill_config_applicability in your instance).2. Locate the applicability record for the skill config that handles field prediction for the relevant use case (e.g., the "classify tasks" or HR field predictor skill config).Direct navigation: https://your-instance.service-now.com/sn_nowassist_skill_config_applicability_list.do?sysparm_query=skill_config.nameLIKEclassify3. Open the applicability record and update the Workflow Name (use case name) field to match the cloned workflow's use case name exactly — in lowercase.Example: if the cloned workflow is named "My Custom HR Predict Workflow", the value must be entered as "my custom hr predict workflow".4. Save the record.5. Test the cloned workflow in the AI Agent Studio playground and verify that field prediction now completes successfully.Note: Only one applicability record per use case name should exist. Duplicate applicability records pointing to the same use case name will cause the agent to pick up the wrong config at runtime. OPTION 2 — Create a New Skill Config for the Cloned Workflow (Recommended for multiple concurrent workflows)Use this option if both the OOB workflow and the cloned workflow need to run independently, or if the cloned workflow requires different configuration values (e.g., different AIS profile, GAF config, or variable set).Steps:1. Navigate to Now Assist > Administration > Skill Configs and open the existing skill config that is used by the OOB workflow for field prediction.Direct navigation: https://your-instance.service-now.com/sn_nowassist_skill_config_list.do2. Review the existing skill config structure — note the following related list records which must be replicated:- Now Assist Skill Config Variable Set- Now Assist Skill Config Applicability- Now Assist Config Status3. Create a new sn_nowassist_skill_config record with the same configuration values as the OOB skill config, adjusting any fields specific to the cloned workflow.4. In the related lists of the new skill config record, create:- A new Now Assist Skill Config Variable Set record (mirroring the OOB values or customizing as needed).- A new Now Assist Skill Config Applicability record with the Workflow Name (use case name) set to the cloned workflow's use case name in lowercase.- A new Now Assist Config Status record to activate the skill config.5. Ensure no other applicability record uses the same use case name as your cloned workflow — duplicates will cause runtime conflicts.6. Test the cloned workflow in the AI Agent Studio playground and verify that field prediction completes successfully.