Clean up stuck notifications in Sparkrock 365

Information

• Product: Sparkrock 365
• Summary: How to clear old email notifications that are stuck in Sparkrock 365 and make sure notifications are set up correctly.

Details

Sparkrock 365 and MySparkrock send email notifications for events such as document approvals and absence requests. If the email server has an outage or the setup is incorrect, these notifications can get stuck and are not sent.

Each time a new notification is triggered, the system first tries to send the stuck ones. If the underlying problem is still there, it fails again and more notifications pile up.

You may also see the error "Email failed to send. Please configure Notification User Name on mySparkrock Solution Setup for notifications." Step 2 below fixes this.

Resolution

We recommend completing these steps with a user who has SUPER permissions.

Check the setup

1. Open Approval User Setup and confirm every Sparkrock 365 user is listed and has an email address.
2. Open mySparkrock Solution Setup and make sure Notification User Name is filled in with a user that can send email. This automatically creates the recurring job queue entry (Object ID 1509) that sends notifications. If notifications stopped, clear the field and enter the user again to recreate the entry.
3. If Job Queue Entries still has an entry for Object ID 23022111, delete it. It's no longer used.

Clear the stuck notifications

We recommend trying steps 4 to 9 in a sandbox first.

4. Create a new configuration package (don't reuse an existing one) with Table ID 1511, and turn on Delete Table Records Before Processing.
5. Select Excel > Export to Excel and open the file.
6. In the Excel file, delete every row from row 4 down, except the last row. Save the file.
7. Back in Sparkrock 365, select Excel > Import from Excel and choose the file.
8. On the pop-up, select Import, then Functions > Apply Data.
9. When asked to confirm, select Yes. A confirmation message like this appears:
   

When you're done, Notification Entries should show only a few records or none, and email notifications should start sending again.

Impact / Risks

Configuration packages can change data in other tables if they're set up incorrectly. Creating a new package with only Table ID 1511, as described in step 4, avoids this.

Workaround

Not applicable.

Related Information

Not applicable.

Update History