Snowflake Connector for ServiceNow® V2 release notes for 2026¶
This topic provides release notes for the Snowflake Connector for ServiceNow® V2. For additional information, see Snowflake Connector for ServiceNow.
Version 5.29.1 (October 28, 2026)¶
Behavior changes¶
Not applicable.
New features¶
Not applicable.
Bug fixes¶
- Fixed an issue where the
EXPORT_CONNECTOR_STATEprocedure and the scheduled state export failed with the errorCannot parse sync state json value fetched from database to object. This issue occurred after the deletions synchronization of a table processed journal entries on version 5.29.0. The connector now exports and imports the new fields of the deletions synchronization state. After you upgrade, call theEXPORT_CONNECTOR_STATEprocedure again, or wait for the next scheduled export. For more information, see Exporting the connector state.
Version 5.29.0 (October 23, 2026)¶
Behavior changes¶
- Requests that return invalid JSON are now retried once after 30 seconds. If the retry also fails, the connector reduces the page size. Previously, the connector reduced the page size immediately. For more information, see Configure the size of a single page fetch for a table.
- The
INGESTED_ROWSvalue in theCONNECTOR_STATSview is now 0 forDELETESruns that find no new journal entries. Previously, it counted the duplicateDELETEevents that those runs inserted again. This change doesn’t indicate lost progress.
New features¶
- Added the
CONFIGURE_EXCLUDE_INACTIVE_COLUMNS_FROM_VIEWSstored procedure. When set totrue, columns that are inactive or deleted in the ServiceNow®sys_dictionarytable are excluded from the__viewand__view_with_deletedviews the next time the connector creates the views. The setting doesn’t apply to tables with column filtering. You must recreate__view_with_referencesviews with theCREATE_VIEW_WITH_DISPLAY_VALUESstored procedure for the change to apply to them. The default isfalse, which preserves the existing behavior. For more information, see Exclude inactive columns from views.
Bug fixes¶
- Fixed an issue where calling the
CONFIGURE_DISPLAY_VALUE_FETCHING,CONFIGURE_SCAN_EVENT_LOG_IN_INCREMENTAL, orCONFIGURE_CHECK_LINK_IN_VIEW_WITH_REFERENCESstored procedure withNULLstoredfalseinstead of returning anINVALID_CONFIGURATIONerror. - Fixed an issue where ingestion didn’t reduce the page size when the External Access function ran out of memory.
Tables with large rows kept failing with the error
Function available memory exhausted. For more information, see Configure the size of a single page fetch for a table. - Fixed an issue where the deletions synchronization inserted the
DELETEevents of the most recently processed journal entries again on every run, as long as no newer journal entry appeared. The connector still rescans the last second of the journal to catch late-arriving entries, but it now skips the entries it already processed for that second. The connector doesn’t remove duplicateDELETEevents that are already in the__EVENT_LOGtable.
Version 5.28.3 (October 7, 2026)¶
Behavior changes¶
Not applicable.
New features¶
Not applicable.
Bug fixes¶
- Fixed an issue where the
CHECK_ROW_COUNTprocedure’smax_sys_created_onfilter always reported a Snowflake row count of 0 if global display value fetching was enabled.
Version 5.28.2 (September 11, 2026)¶
Behavior changes¶
Not applicable.
New features¶
Not applicable.
Bug fixes¶
- Fixed an issue where calling the
CONFIGURE_SCAN_EVENT_LOG_IN_INCREMENTALstored procedure withFALSEdidn’t reduce__EVENT_LOGtable scanning during deletions synchronization the way it did for inserts and updates. On accounts with a large__EVENT_LOGtable, this issue could cause the connector to scan the entire table for every batch of the deletions journal. - Fixed an issue where the
CHECK_ROW_COUNTprocedure’smax_sys_created_onfilter always reported a Snowflake row count of 0 for connectors that have display value fetching enabled.
Version 5.28.1 (August 19, 2026)¶
Behavior changes¶
Not applicable.
New features¶
Not applicable.
Bug fixes¶
- Fixed an issue where ingestion or a table reload could retry indefinitely with the same page size after the ingestion procedure ran out of memory. The connector now reduces the page size before retrying.
- Fixed a data-loss issue in tables that have row filtering enabled. When ServiceNow® returned no rows in response to a
query for records with an empty
sys_updated_onorsys_created_onvalue, the connector could delete every row in the table. - Fixed an issue where the incremental update window didn’t advance when a run fetched no rows. The window collapsed to zero width, which prevented any further records from being ingested for the affected table.
- Fixed the same issue in the deletions synchronization window. This issue caused every subsequent run to rescan the journal table from an outdated timestamp.
- Fixed an issue where the connector didn’t warn when it skipped records whose
sys_updated_onorsys_created_onvalues it couldn’t read. For example, a ServiceNow® field-level access control list can hide either column from the connector user. If an access control list caused records to be skipped, correct the list and then reload the affected tables with theRELOAD_TABLEprocedure. For more information, see Reload data in a table.
Version 5.28.0 (June 29, 2026)¶
Behavior changes¶
Not applicable.
New features¶
- Added the
CONFIGURE_SCAN_EVENT_LOG_IN_INCREMENTALstored procedure. When set tofalse, incremental ingestion no longer probes the__EVENT_LOGtable to classify each fetched row as anINSERTorUPDATE. On accounts with large__EVENT_LOGtables, doing so avoids scanning a large amount of data during every batch. The default istrue, which preserves the existing behavior. For more information, see Configure the event log scan during incremental ingestion. - Added the
CONFIGURE_CHECK_LINK_IN_VIEW_WITH_REFERENCESstored procedure. When set tofalse, views created using theCREATE_VIEW_WITH_DISPLAY_VALUESstored procedure do not check thelinkproperty of the raw ServiceNow® row, which lets you use non-standard reference links. The default istrue, which preserves the existing behavior. For more information, see Configure reference link checking for views. - Added support for checking empty values in row filtering, for example,
u_name = "". For more information, see Enable a single table by using row filtering.
Bug fixes¶
Not applicable.
Version 5.27.4 (March 5, 2026)¶
Behavior changes¶
Not applicable.
New features¶
Not applicable.
Bug fixes¶
- Fixed an issue that caused alert emails to be sent too often and with incorrect error data.
Version 5.27.3 (February 17, 2026)¶
Behavior changes¶
Not applicable.
New features¶
Not applicable.
Bug fixes¶
- Fixed a possible race condition during the reload finalization process.
Version 5.27.2 (January 21, 2026)¶
Behavior changes¶
Not applicable.
New features¶
Not applicable.
Bug fixes¶
- Fixed an issue where display values were not processed correctly when ingesting rotated tables.
- Improved logging in the alerting system.