Australia Issues - Notifications not working after clone

[athavichith]

Anyone else hates the Australia versions same as me?  We been having so many issues with Australia ever since upgrading to the version. 

The issue we are facing now, is we did a clone to our Test and Dev environments. And now our notifications are not working. The notifications should be sitting in our Outbox. 

I created a HI Support case for them to look at it but asking the community if anyone has dealt similar issue. 

Thank you

[Tanushree Maiti]

Hi @athavichith 

After an instance clone, ServiceNow disables email sending in non-production environments (like Dev and Test) by default to prevent accidental emails from reaching real users.

Did you check KB0547597 Post-Cloning Checklist  . If not check it once.

• Type Email properties in Application navigator and ensure Email sending enabled checkbox is checked if you want them to leave the outbox ( Though it is not recommended in non-prod)

• To enable email:

  1. Navigate to System Properties > Email.
  2. Configure the email properties:
     
     • Enable email sending (SMTP) (glide.email.smtp.active😞 Yes
     • Enable email sending (POP3) (glide.email.read.active😞 Yes

     For more information, see Email Properties in the product documentation.

  3. Click Save.
• https://www.youtube.com/watch?v=GBpjCJe5ZgE&t=14s

[athavichith]

From ServiceNow, this is known problem. 

[athavichith]

As per our investigation, we observed the events were not getting processed properly as the jobs and configuration for the events queue module were not correct after the recent clone happened on the instance. This issue was caused by a known problem, PRB2080045, where a node running a mismatched release during the Processing Framework migration can cause the framework to create legacy or incorrect jobs. This resulted in invalid event queue triggers, specifically for the protected DEFAULT queue which could not be manually recreated by the customer.

PRB2080045 will be fixed in future releases.

Once we applied the workaround using CHG78668963 the events queue jobs configuration was corrected and the events started to process normally now.

[mathewhayde]

This is helpfull