Access Refused to Event 'sn_hr_core_case.updated' in HR Core Scope on New Prod Instance

Satyam123
Tera Contributor

I'm encountering an error in my new production instance that doesn't occur in development:

"Access to event 'sn_hr_core_case.updated' from scope 'Human Resources: Core' has been refused. The event is not defined."

This happens when performing certain actions (e.g., updating HR cases), but the same workflow works fine in the dev environment.

2 REPLIES 2

NavyaMasapu
Tera Contributor

This error usually occurs when the event you are trying to trigger doesn’t exist or isn’t accessible in the current scope:

Here are a few things to verify:

 

  1. Missing Event Definition in Production

    In your dev environment, go to System Policy > Events > Event Definitions, and search for sn_hr_core.case.updated.

    If it’s there but missing in prod, it likely didn’t move over during deployment. You’ll need to include it in an update set and deploy it to prod.

  2. Cross-Scope Access

    If the code triggering the event is in a different scope than where the event is defined (e.g., your script is in a custom app calling an HR Core event), make sure:

     

    • The event is public, or

    • You’ve granted cross-scope access for that API call.

     

  3. Deployment Validation

    Sometimes, the workflow or script in dev refers to custom events that weren’t promoted correctly. Recheck your deployment steps or update sets.

Please let me know if any further help needed!
Also, please mark Helpful if this helped you to resolve your issue. Thankyou!

GlideFather
Tera Patron

Hi @Satyam123 it is most likely the cross scope issue, try to investigate but if it is PROD, go and raise HI Case for ServiceNow team to help you with that. Usually they respond very quickly. 

 

  • Go to: https://support.servicenow.com/now 
  • SSO or Login
  • Click Get support,
  • scroll down until the Looking for something else? box located in right bottom corner,
  • there is "Create case" button.

That is where you need to go with PROD issues.

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */