- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2025 04:00 AM
I have cloned the OOTB Case Summarization skill along with its associated AI Prompt, published both, and activated the cloned skill in Now Assist Admin. The activation shows that the cloned skill is active and the original OOTB skill is deactivated. However, when I test case summarization using the Summarize button, it still returns the old OOTB response. Interestingly, the cloned skill works correctly when tested independently. Has anyone faced a similar issue or know if there's a configuration I'm missing? Would appreciate insights if you've worked on this.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2025 02:50 AM
Hey everyone! 😊
Just wanted to share a quick tip that helped me resolve this issue. If you're cloning a skill from the Now Assist Skill Kit and it's not working as expected after activation — here's the trick:
👉 Start by cloning the skill from the Now Assist Admin module, and then head over to the Skill Kit to make your custom updates.
It’s a small change in the process, but it makes a big difference! Once I followed this flow, everything worked smoothly. Hope this helps anyone else running into the same hiccup!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi @_Yash24 ,
A couple of things you can verify:
Check if the Summarize button is visible by default.
If it isn’t visible at all, ensure that the OOTB UI Action “Summarize” is activated.
This needs to be enabled either in Workspace or Core UI, depending on where you want to use it.Update Set considerations:
Moving the changes through an update set is fine, but ensure every related record is captured.
AI features have multiple dependency tables and linked configurations—missing even one can cause unexpected behaviour like buttons not appearing.Skill configuration:
Confirm that the skill is published, active, and the conditions/roles required to access the skill are correctly configured in the QA instance.
If you confirm these points, it should help identify why the button appears in Dev but not in QA.
Let me know what you find, and we can investigate further.
