Table Cleaner Stopped working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2024 03:40 PM
Table Cleaner stopped working, it appears to have timed out. Basically, If table cleaner rule has a query that takes longer than 30 seconds to complete, the entire table cleaner job is stopped and by default, table cleaner waits two days before table cleaner job runs again.
So Is there any way to run table cleaner again without having to wait the two days ?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2024 04:38 PM
How many records do you have? Just open the table configuration and click Delete Records button.
Or if you want to selectively delete, write a fix script with deleteMultiple().
You don't have to wait 2 days, or use the Table Cleaner at all 😉
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2024 04:43 PM
Hi Priya,
Did you got a chance to review the property "glide.db.tablecleaner.chunk_delete_max_time_spent" ?
Link: https://docs.servicenow.com/bundle/washingtondc-platform-administration/page/administer/managing-dat...
Hope this property helps.
Thanks,
Dhruv

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2024 08:45 PM
Hi there,
Table Cleaner itself doesnt wait for 2 days. Only that specific rule waits for 2 days, or that's what I thought. Table Cleaner should just run according to the normal interval which is usually 1 hour.
If you want to influence the slow rule attempt:
|
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2024 10:06 AM
But slow rule attempt property will impact all auto flush rules and I do not want that. Is there anything can I do with specific rule so that it can run again ?