Now assist skill is not loading

Lovely2134
Tera Contributor

3 weeks ago

Whenever I try to open the Now Assist skill in the sfsbx instance, my instance goes down.

Preview file
34 KB
0 Helpfuls
  • 282 Views
2 REPLIES 2

Tanushree Maiti
Kilo Patron

3 weeks ago

Hi @Lovely2134 

 

As an Admin, check following things:

1. Navigate sys_generative_ai_log.list for errors when the error has  encountered

2. Check Browser Console  to check  for JavaScript errors 

3. If the skill is running as an interactive or immediate background task, you can terminate it directly.    

  • Navigate to Active Transactions: Go to System Administration > All Active Transactions in your instance.
  • look for entries related to now_Assist_skill_kit
  • Kill it

 3)Go to System Scheduler > Scheduled Jobs or look for specific Now Assist skill kit scheduled jobs.

     Cancel the active jobs.

 

 

2.

Please mark this response as Helpful & Accept it as solution if it assisted you with your question.
Regards
Tanushree Maiti
ServiceNow Technical Architect
Linkedin:
0 Helpfuls

SohamTipnis
Mega Sage

3 weeks ago

Hi @Lovely2134,

 

This is definitely not normal behavior, and honestly, it doesn’t look like something you’re doing wrong.
Whenever opening a Now Assist skill brings down the entire sandbox instance, it usually points to a backend issue: either the plugin setup isn’t complete or the instance doesn’t have enough resources to handle it. Sandbox (sfsbx) instances are pretty limited, and AI features like Now Assist can sometimes overload them.
A good starting point would be to quickly check the system logs right after the crash and see if any memory or script-related errors show up. Also make sure all required Now Assist and GenAI-related plugins are properly installed and not in a partial state.
If everything looks fine from your side and the issue is still happening consistently, then it’s most likely an instance-level problem. In that case, raising an HI ticket with ServiceNow is the best move; they can check node stability and backend failures.

 

Refer to this documentation: https://www.servicenow.com/docs/r/impact/register-your-instance.html


In short, this is more of a platform or environment limitation issue rather than a mistake in your configuration.

 

Let me know if it works!!! 😉

 

If you find my answer useful, please mark it as Helpful and Correct. ‌‌‌‌😊


Regards,
Soham Tipnis
ServiceNow Developer || Technical Consultant
LinkedIn: www.linkedin.com/in/sohamtipnis10

0 Helpfuls