Clonned OOTB Case Summarization Skill not working

[snehasriniv]

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.

[Dr Atul G- LNG]

Hi @snehasriniv 

Try cache.do and if still issue better log a now support case.

[snehasriniv]

Hi Atul,

I have already tried cache.do and still there is no change in response. There are actually 2 default Prompts in LLM in the Clonned Skill. Could this be an issue? If so, is there a way to remove default for one of the prompts.

[snehasriniv · Accepted solution]

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! 

[_Yash24]

Hi @snehasriniv 

I have done the same, I have made a copy of change summarization and made changes to skill and then saved it but still Summarize button is not visible in QA instance, It worked perfectly in Dev instance.
I have captured everything in update set and same has been moved.
Pannel is working as expected but on change request form Summarize button is not visible.
What could be the issue here?

what is recommended- You should capture changes in update sets or you should do it manually in every instance?

looking forward to your response.