Observing numerous error message ' GlideDate *** ERROR *** Unparseable date: "XXXXX" ' in the syslog table and localhost log fileIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } You may have found a similar Unparseable date error being created in the syslog table and the localhost log file from various user transactions. If this exception/error occurs frequently, it is causing the syslog table to grow unexpectedly large. It could also cause part of the localhost log file to be truncated once the file size exceeds 6 GB, and this may impact the troubleshooting, as some messages are being deleted from the file. Sample Exception : 2026-04-13 14:51:48 (527) API_INT-thread-41 A22DB9A8EB584F50A5F6FD2BCAD0CDFF txid=2a2dfda8eb58 GlideDate *** ERROR *** Unparseable date: "202" java.text.ParseException: Unparseable date: "202" at java.base/java.text.DateFormat.parse(DateFormat.java:399) at com.snc.commons.datetime.SNCSimpleDateFormatEx.parse(SNCSimpleDateFormatEx.java:133) at com.glide.util.SimpleDateFormatEx.parse(SimpleDateFormatEx.java:38) at com.glide.glideobject.GlideDate.setValue(GlideDate.java:161) at com.glide.glideobject.GlideDateTime.setInitialValue(GlideDateTime.java:1813) at com.glide.script.glide_elements.GlideElementGlideObject.setInitialValue(GlideElementGlideObject.java:242) at com.glide.script.GlideElement.newGlideElement(GlideElement.java:197) at com.glide.script.GlideRecord.loadRow0(GlideRecord.java:4552) at com.glide.script.GlideRecord.loadRow(GlideRecord.java:4370) at com.glide.script.GlideRecordSecure.loadRow(GlideRecordSecure.java:196) at com.glide.script.GlideRecord.next(GlideRecord.java:7886) at com.glide.script.GlideRecordSecure.next(GlideRecordSecure.java:635) at com.glide.rest.util.GlideRecordIterator.next(GlideRecordIterator.java:27) at com.glide.rest.handler.impl.ServiceResultHandlerImpl.serializeIterable(ServiceResultHandlerImpl.java:122) at com.glide.rest.handler.impl.ServiceResultHandlerImpl.processServiceResultBody(ServiceResultHandlerImpl.java:104) at com.glide.rest.handler.impl.ServiceResultHandlerImpl.processServiceResult(ServiceResultHandlerImpl.java:44) at com.glide.rest.processors.RESTAPIProcessor.processInternal(RESTAPIProcessor.java:471) at com.glide.rest.processors.RESTAPIProcessor.process(RESTAPIProcessor.java:453) at com.glide.processors.AProcessor.runProcessor(AProcessor.java:916) at com.glide.processors.AProcessor.processTransaction(AProcessor.java:342) at com.glide.processors.ProcessorRegistry.process0(ProcessorRegistry.java:200) at com.glide.processors.ProcessorRegistry.process(ProcessorRegistry.java:188) at com.glide.ui.GlideServletTransaction.process(GlideServletTransaction.java:62) at com.glide.sys.Transaction.run(Transaction.java:3184) at com.glide.ui.HTTPTransaction.run(HTTPTransaction.java:44) at com.glide.sys.util.sema.SemaphoreQueueThreadPool$Semaphore.runTransaction(SemaphoreQueueThreadPool.java:338) at com.glide.sys.util.sema.SemaphoreQueueThreadPool$Semaphore.runThreadImpl(SemaphoreQueueThreadPool.java:303) at com.glide.sys.util.sema.SemaphoreQueueThreadPool$Semaphore.runThread(SemaphoreQueueThreadPool.java:150) at java.base/java.lang.Thread.run(Thread.java:841) Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } N/A Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } One possible cause is the misconfiguration in the table columns with the 'Date' or 'Date/Time' type. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Review the Dictionary module and check if any 'Date' or 'Date/Time' typed table columns are enabled for Function Field and have info configured in the 'Function definition' field. Function fields do not have an associated database column. Instead, function fields generate a value based on simple computations of other fields and constants. If the Function Definition has the incorrect info configured for the 'Date' or 'Date/Time' typed table columns, the platform will throw an 'Unparseable date' exception. For example, configure 'glidefunction:substring(sys_created_on,0,4)' in the 'Function definition' field for a 'Date' typed column and expect it to return the Year value like '2026', but actually it returns '202' and throws 'GlideDate *** ERROR *** Unparseable date: "202"' exception in the log. This is because the glidefunction:substring() takes a text field and two whole numbers as input. Returns the first instance of a string that starts at the position of the first whole number and is of the length of the second. The position of the string to start counting is the whole number 1, other than 0. Correct the value to 'glidefunction:substring(sys_created_on,1,4)' in the 'Function definition' field for a 'Date' typed column, which resolved the date parsing error.