Known issues for 10.x
A summary of known issues for Verisk's Touchstone software offering specific to release 10.x.
Note: Touchstone 2025 is 13.0. Touchstone 2024 is 12.0.
Touchstone 2023 is 11.0.
Touchstone 2022 is 10.0.
Touchstone 2021 is 9.0.
Click individual IDs below for more details.
ID | Date posted | Version(s) affected | Resolved | Summary |
---|---|---|---|---|
445 | 5/20/2025 | 12.2, 12.0, 11.5, 10.0 | Future Verisk Synergy Studio release | Coverage D limits are applied for CB (combined, excluding time) type limits if they are coded. |
437 | 3/20/2025 | 12.2.3, 12.2, 12.0, 11.5 | Touchstone 2025 (13.0) | Back-allocation for loss results from Workers Comp' exposures with Min/Max/MinMax sublimits is not working as expected. |
435 | 3/20/2025 | 13.0, 12.2.3, 12.2, 12.0, 11.5, 11.2, 11.0, 10.0 | If you have run a loss analysis which includes the Verisk Severe Thunderstorm Model for Canada Event Loss Summary table displays only U.S. states in the Max Affected Areas field and not the Canada Severe Thunderstorm events. | |
399 | 5/7/2024 | 11.5, 11.2, 11.0, 10.0, 9.0 | Touchstone 2024 (12.0) | When imported perils are coded for PWX and PWH in one location term, they will be transposed upon export to include the additional peril PWA. |
398 | 5/7/2024 | 11.5, 11.2, 11.0, 10.0, 9.0 | Touchstone 2024 (12.0) | Touchstone geocoding does not support LocationPrecision code=19 if the Premium geocoder is used. |
386 | 2/29/2024 | 11.5 | Touchstone 2024 (12.0) | When a mini-policy (MP) deductible is present on a location and the contract has layers and sub-limits and the analysis is run with specific save results [by location] and [save by coverage] then total Gross losses are not accurately back-allocated to coverage. Total Gross by location is correct. |
384 | 2/29/2024 | 11.5 | Touchstone 2024 | Min/Max NGM terms do not apply for Geospatial analysis with Workers' Compensation exposure. |
382 | 2/29/2024 | 11.5, 11.2, 10.0 | Touchstone 2024 | Total Replacement Value (TRV) is calculated incorrectly if the exposure has multiple currencies or the project currency is not the same as the display base currency. |
379 | 1/17/2024 | 10.0 | Touchstone 10.0.15 | In a very specific set of circumstances, the Verisk Severe Thunderstorm Model for the United States will calculate loss incorrectly. |
374 | 7/28/2023 | 10.0, 9.1, 9.0 | Touchstone 2023 (11.0) | Location facultative reinsurance does not apply when disaggregation is triggered. |
370 | 6/15/2023 | 10.0 | Regular updates have continued with the June 2023 release | In Touchstone, the average wage and benefit information for the U.S. Workers Compensation model was not updated in the 2022 release and the values contained in the software do not match those shown in the 2022 Industry Assumptions document found on the client portal. |
368 | 6/15/2023 | 12.0, 11.5, 11.2, 11.0, 10.0, 9.1, 9.0 | Future Touchstone release | Losses for the four Extreme Disaster Scenario events in the Verisk Inland Flood Model for Japan are overstated. |
365 | 6/15/2023 | 12.2.3, 11.2, 11.0, 10.0, 9.1, 9.0 | Touchstone 2023 (11.5) | When users run grid ring analyses in the Geospatial module and the global bounding box is defined to include a negative latitude and a positive longitude, an error message that all exposures were ruled out appears. |
358 | 6/15/2023 | 11.2, 11.0, 10.0 | Touchstone 2023 (11.5) | Incomplete geocoding may occur during Touchstone import when the minimum or maximum number of cores are set to eight. |
355 | 5/1/2023 | 10.0 | Touchstone 2023 (11.0) | When applying a standalone CAT XOL to loss results that were run using the 10K World AP (STD or WSST) event sets, the losses from the Verisk Severe Thunderstorm Model for the United States are excluded. |
354 | 5/1/2023 | 10.0, 9.1, 9.0 | Touchstone 2023 (11.0) | The PerilSetCode in LOSS_ByContractSummary is different from that in LOSS_ByLayer table. This could indicate that different peril sets were used for the analyses performed using these tables. Note that this applies only to analyses run with the Next Generation Models (NGM) engine. |
353 | 2/15/2023 | 10.0, 9.1, 9.0 | Touchstone 2023 (11.0) | When a geospatial Grid Ring analysis is run, the geocode match level code filters are not removing the “None” locations from the results when they should be removed. |
352 | 2/15/2023 | 10.0, 9.1, 9.0 | Touchstone 2023 (11.0) | Custom Demand Surge option selected in the Analysis template does not reflect correctly in the Analysis Options pane. |
351 | 2/15/2023 | 10.0, 9.1, 9.0 | Touchstone 2023 (11.0) | Incorrect API response option is used for custom demand surge setting. |
350 | 11/22/2022 | 12.0, 11.5, 11.2, 10.0, 9.1, 9.0 | Touchstone 2024 | Building (Coverage A) losses for a location may be misstated in the Japan, Caribbean and Australia earthquake models when that location has different values in the Construction Building and Construction Other Structures fields and the Stories field is unknown. |
349 | 10/20/22 | 10.0 | Hot fix 10.0.5 | Analyses run with World AP event sets will fail if precipitation flood is selected, there is U.S. exposure in the exposure view being analyzed, and you do not have U..S Inland Flood or U.S. Hurricane Precipitation Flood licensed. |
348 | 9/8/22 | 10.0 | Touchstone 2023 (11.0) | Venezuela losses with v10 default currency rate table are overstated when viewed in non-Venezuela currency. |
347 | 8/26/22 | 10.0 | Hot fix 10.0.3 | When running the 10K World AP (2022) - Standard - US Severe Thunderstorm CAT only or the 10k World AP (2022) - Warm SST Conditioned Hurricane - US Severe Thunderstorm CAT only event sets the losses for the Verisk Severe Thunderstorm Model for the United States are being calculated using the Standard (All-Event) catalog and will be overstated. |
345 | 8/8/2022 | 10.0 | Hot fix 10.0.3 | In scenarios where the user has run a loss analysis containing the U.S. Severe Thunderstorm model and saved by peril, the results in the user interface show the model info being presented numerically. Losses with subperils in the database are saved with the combined peril set code 11534336 (HL+SW+TD) which is what is being displayed in the results user interface. |
344 | 8/2/2022 | 10.0 | Hot fix 10.0.3 | Resubmitting a World All Peril loss analysis does not generate U.S. Severe Thunderstorm losses. |
343 | 7/11/2022 | 10.0, 9.1, 9.0 | Touchstone 2023 (11.0) | Gross losses are incorrect when layers are coded only for individual sub-perils. |
340 | 6/15/22 | 10.0, 9.1, 9.0 | Touchstone 2023 (11.0) | The Verisk Inland Flood Model for Great Britain can return incorrect losses when that model is run at the same time with the Verisk Extratropical Cyclone Model for Europe for specific occupancy codes and secondary risk characteristic combinations as noted in the detail. |
339 | 6/15/22 | 12.0, 11.5, 11.2, 11.0, 10.0 | Future Touchstone release | Min and Max CPU cores field always show minimum and maximum number of cores respectively for that environment regardless of what is saved by the user or what is in the database. |
336 | 1/19/2022 | 10.0, 9.1, 9.0 | For reinsurance treaties coded for Severe Thunderstorm exported from Touchstone 8.0 as a .rpx into 9.0 and then modified in the Touchstone user interface, subperils are not accounted for during loss analysis. | |
335 | 11/18/2021 | 10.0, 9.0, 9.1 | Touchstone 2022 | Fire following losses for two historical events (1923 Kanto and 1995 Kobe) and government scenario events are understated in the Verisk Earthquake Model for Japan. |
334 | 11/3/2021 | 10.0, 9.0, 9.1 | Touchstone 2022 | Losses for certain historical events in the Verisk Earthquake Model for the United States may be misstated. |
331 | 9/23/2021 | 10.0, 9.1, 9.0 | Touchstone 2023 (11.0) | Some clients are seeing loss analysis failures with a specific error message. |
329 | 8/31/2021 | 10.0, 9.1, 9.0 | Layer gross losses are incorrect when using the revised min-max methodology. | |
328 | 8/31/2021 | 11.0 10.0, 9.1, 9.0 | Touchstone 2023 (11.5) | Custom catalogs created for the Verisk Wildfire Model for the United States cause analysis failures. |
323 | 7/9/2021 | 11.2,11.0, 10.0, 9.1, 9.0 | User-supplied postal data are not being retained if provided data has SubArea2 information for New Zealand data. | |
322 | 7/9/2021 | 11.2,11.0, 10.0, 9.1, 9.0 | CLF numbers are being generated incorrectly for Indonesia postal codes. | |
321 | 6/15/2021 | 11.2,11.0, 10.0, 9.1, 9.0 | Event description information is not loaded properly in the Event Loss Summary table for Terrorism loss analysis results run against custom event sets. | |
320 | 6/15/2021 | 11.2,11.0, 10.0, 9.1, 9.0 | When running the Verisk Earthquake Model for Japan the Epicenter Area field is missing a subarea entry in the Event Description for a small number of events. | |
319 | 6/15/2021 | 11.2,11.0, 10.0, 9.1, 9.0 | Geospatial accumulation by zone does not work properly when the damage ratio for the zone is not 100% for zones created in previous Touchstone versions. | |
316 | 2/4/2021 | 10.0 | For exposures with an unknown number of stories, losses produced by the Verisk Inland Flood Model for Central Europe exhibit a systematic over- or under-estimation depending on the modeled country. | |
309 | 10/2/2020 | 11.2, 11.0, 10.0, 9.1, 9.0 | Southern extent of Verisk Bushfire Model for Australia ends at 43S latitude excluding portions of Tasmania. | |
304 | 7/10/2020 | 11.2, 11.0, 10.0, 9.1, 9.0 | Project Export: Export is failing when the CLF base file name exceeds the range of 260 characters. | |
303 | 7/10/2020 | 11.2, 11.0, 10.0, 9.1, 9.0 | Comparative Analysis and CSV/DB exports are disabled for loss results that are attached to an 8.0 environment. | |
302 | 7/10/2020 | 11.2, 11.0, 10.0, 9.1, 9.0 | In some cases when users execute Touchstone on a remote machine, the text associated with checkboxes in a drop-down list is not readable or appears trimmed. | |
301 | 7/10/2020 | 11.2, 11.0, 10.0, 9.1, 9.0 | In the Verisk Earthquake Model for Caribbean, most Touchstone event descriptions show an incorrect value in the 'MArea' and 'EArea' fields. | |
300 | 7/10/2020 | 11.2, 11.0, 10.0, 9.1, 9.0 | Assigning a value of -1 to the Floor of Interest secondary modifier will produce loss when the Foundation Type is not a basement in the Verisk Inland Flood Model for the United States and the Storm Surge and Precipitation Flood sub-perils of the Verisk Hurricane Model for the United States. | |
299 | 7/10/2020 | 11.2, 11.0, 10.0, 9.1, 9.0 | Certain flood secondary risk characteristics will affect losses for Builder's Risk exposure in the Verisk Inland Flood Model for the United States and the Storm Surge and Precipitation Flood sub-perils of the Verisk Hurricane Model for the United States. when they should not. | |
298 | 7/10/2020 | 11.2, 11.0, 10.0, 9.1, 9.0 | Project Completion and Project Phase fields are ignored for Builder's Risk exposure when running precipitation flood only in the Verisk Hurricane Model for the United States. | |
297 | 7/10/2020 | 11.2, 11.0, 10.0, 9.1, 9.0 | Inaccurate Coverage C losses occur when modeling marine cargo exposure where the construction codes for building and other structures are not the same in the Verisk Typhoon Model for Japan. | |
296 | 7/10/2020 | 11.2, 11.0, 10.0, 9.1, 9.0 | Under certain circumstances, loss output may be incorrect because certain Foundation Types instead of Foundation Connections are being utilized for loss calculations for Industrial Facilities (400 series) in the Verisk Earthquake Model for New Zealand. | |
256 | 8/1/2018 | 11.2, 11.0, 10.0, 9.1, 9.0 | Damage for certain construction codes for the Verisk Inland Flood Model for Southeast Europe is not increasing in an expected way for exposures that have a height of nine stories or more. | |
249 | 8/1/2018 | 11.2, 11.0, 10.0, 9.1, 9.0 | When using contract level geospatial analysis on a filtered exposure view show the full view results rather than those of the individual contract. | |
244 | 8/1/2018 | 11.2, 11.0, 10.0, 9.1, 9.0 | Offshore CLF export fails for individual treaties and some specific financial perspectives. | |
241 | 8/1/2018 | 11.2, 11.0, 10.0, 9.1, 9.0 | Losses generated by the Verisk Inland Flood Model for Great Britain for unsupported foundation types are not intuitive. | |
239 | 8/1/2018 | 11.2, 11.0, 10.0, 9.1, 9.0 | On importing Workers' Compensation exposure with blank shift percentages, incorrect default values are being applied. | |
233 | 4/30/2018 | 10.0, 9.1, 9.0 | The definition of square footage for occupancy 303 in the Verisk Earthquake Model for the United States has changed to refer to the area of an entire building to be consistent with Verisk Hurricane Model for the United States. The previous definition in the Verisk Earthquake Model for the United States was the area of single unit only. | |
147 | 8/8/2016 | 11.2, 11.0, 10.0, 9.1, 9.0 | For those clients running a Hazard analysis, it is important to note that if you want to run the analysis on more than one core, you must set the minimum and maximum number of cores to the same number. | |
140 | 6/15/2016 | 11.2, 11.0, 10.0, 9.1, 9.0 | Export loss to CSV will fail when the analysis has been run with the MAOL option selected and the export also has the MAOL option selected. | |
138 | 6/15/2016 | 11.2, 11.0, 10.0, 9.1, 9.0 | Puerto Rico UNICEDE Values Incorrect Due to Interpretation of Municipality Codes as CRESTA codes |