Known issues for 11.x
A summary of known issues for Verisk's Touchstone software offering specific to release 11.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 |
|---|---|---|---|---|
| 448 | 8/13/2025 | 13.0 | Future Verisk Synergy Studio release | LLEI analyses using the Verisk Inland Flood Model for the UK and the Republic of Ireland are outputting results for "no velocity" intensities. |
| 447 | 8/13/2025 | 13.0, 12.0, 11.5, 11.0, 10.0 | Future Verisk Synergy Studio release | The database field IsTemplateCustomized does not reflect whether a template was modified or not. |
| 446 | 8/13/2025 | 13.0, 12.0, 11.5, 11.0 | Future Verisk Synergy Studio release | Surplus share treaties cannot have multiple risk-level attachments and limits for the same contract/layer/location. |
| 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. |
| 444 | 5/20/2025 | 12.2, 12.0, 11.5 | Touchstone 2025 (13.0) | LOSS_ByTreatyExposureAttributeGeo result tables, and consequently treaty CLFs have more rows than expected. |
| 442 | 4/16/2025 | 12.0, 11.5, 11.0 | Touchstone 2025 (13.0) | Ground-up losses can vary for combined peril exposures when Loss Modification Factor (LMF) rules have different factors across overlapping regions or peril combinations. |
| 440 | 4/16/2025 | 12.0, 11.5 | Touchstone 2025 (13.0) | In the Geospatial Analysis, locations that are not tagged within a sublimit are ignored for gross loss calculation when there is a Minimum deductible. |
| 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. | |
| 433 | 1/24/2025 | 12.2.3, 12.2, 12.0, 11.5 | Touchstone 2025 (13.0) | Exposures with very large contracts can produce incorrect gross loss, when saved by layer/geo or layer/zone. |
| 432 | 12/13/2024 | All versions. | Due to certain centroids of the 7-digit post codes for the UK falling in water bodies (e.g. piers), it is possible for large storm surge losses to be generated for Great Britain. | |
| 431 | 12/13/2024 | 12.2.3, 12.2, 12.0 | Touchstone 2025 (13.0) | Users may see incorrect losses when custom templates that have been upgraded from a prior release are used in v12.0. |
| 430 | 12/13/2024 | 12.0, 11.5 | Touchstone Hot Fix 12.2.3 | Exports of exposure with nested sublimits may fail with a specific error message. |
| 429 | 11/21/2024 | 12.2.3, 12.0, 11.5, 11.0 | Touchstone 2025 (13.0) | Gross loss produced in v12 with zero Participation Limit percent. |
| 427 | 11/21/2024 | 12.2.3, 12.2, 12.0, 11.5, 11.0 | Touchstone 2025 (13.0) | Coverage back-allocation is improved with NGM for event totals (e.g. byEvent table, byLayer table). This leads to a mismatch between coverage losses within byEvent / byLayer table and coverages in byLocation tables (byLocation still uses the pre-NGM logic). |
| 426 | 11/21/2024 | 12.2.3, 12.2, 12.0, 11.5, 11.0 | Touchstone 2025 (13.0) | When coding step functions and using trigger type 4, the calculation of the content steps can be incorrect for any content steps that are not the first content step. |
| 422 | 10/7/2024 | 12.2.3, 12.0, 11.5 | Touchstone 2025 (13.0) | Treaty aggregate terms are not exhausted correctly for most treaty peril codings that do not cover all perils that are run in the analysis. |
| 418 | 10/2/2024 | 12.2.3, 12.2, 12.0, 11.5, 11.0 | Future Verisk Synergy Studio release | A discrepancy in the calculation of treay losses can be seen when running CAT XOL analyses resulting in a numbers difference depending on the save by options selected. |
| 416 | 7/30/2024 | 12.0, 11.5 | Touchstone 12.2.0 Service Pack | When an exposure has contracts with varying tiers of sublimits and Min/Max/MinMax deductibles on some of the sublimits, the exposure will produce incorrect gross loss. |
| 415 | 7/10/2024 | 12.2.3, 12.0, 11.5, 11.2, 11.0, 10.0, 9.1, 9.0 | Touchstone 2025 (13.0) | In some cases nested sublimits can produce incorrect loss with column-wise coding. |
| 413 | 7/1/2024 | 12.0, 11.5, 11.0 | Touchstone 12.2.0 Service Pack | After exporting exposure to a database, the OccParticipation% for all contracts changes to 0 resulting in unexpected loss results. |
| 412 | 7/1/2024 | 12.2.3, 12.0 11.5 | Touchstone 2025 (13.0) | When a user selects to use the CLF Compatibility function within the loss analysis configuration screen for standalone CAT XOL analyses, invalid results are produced in Touchstone Re. |
| 410 | 6/14/2024 | 12.2.3, 12.0, 11.5 | Touchstone 2025 (13.0) | Exposure Summary does not populate all perils when multiple perils are present at the location level. |
| 409 | 6/14/2024 | 12.2.3, 12.0, 11.5 | Touchstone 2025 (13.0) | When CATXOL analyses are run, there are certain scenarios based on exposure, reinsurance coding and save by options, where there is loss difference observed between the various backend tables due to incorrect calculations at various levels. This issue does not exist with Ground Up, Gross, or PreCATNet Loss perspectives. |
| 408 | 6/14/2024 | 12.0, 11.5 | Touchstone 12.2.0 Service Pack | Layer max losses are incorrect when Sublimit's PerilSetCode is different than Layer's PerilSetCode |
| 407 | 6/14/2024 | 12.0, 11.5 | Touchstone 12.2.0 Service Pack | ByLocationSummary and ByContractSummary table may contain extra rows when saving by peril. |
| 406 | 6/14/2024 | 12.0, 11.5 | Touchstone 12.2.0 Service Pack | By ContractLayerGeo table is incorrect when saving by claims. |
| 405 | 6/14/2024 | 12.0, 11.5 | Touchstone 12.2.0 Service Pack | ByTreatyExposureAttribute table for Location UDF is incorrect for layer treaties. |
| 404 | 6/14/2024 | 12.0, 11.5 | Touchstone 12.2.0 Service Pack | ByLayer is incorrect without vs with Pre-LayerGross for Treaties on Layer & Contract, with LOB filter. |
| 403 | 6/14/2024 | 12.2.3, 12.0, 11.5 | Touchstone 2025 (13.0) | In Loss modification factor template, multiple factors are getting applied for Admin Boundary with Coverage and LOB. |
| 402 | 6/14/2024 | 12.2.3, 12.0, 11.5 | Touchstone 2025 (13.0) | When results are saved with option EP curve by peril, the combined peril EP curve in summary results table is not created unless two models share a common perilset code |
| 401 | 6/14/2024 | 12.0, 11.5 | Touchstone Hot Fix 12.2.3 | In Geospatial analysis, the LocLimitType C with a blank value is not applying correctly. |
| 400 | 6/14/2024 | 12.2.3, 12.0, 11.5 | Touchstone 2025 (13.0) | In geospatial analyses, min/max deductibles are not applied for nested sublimits when deductible is applied to a parent sublimit. |
| 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. |
| 397 | 5/7/2024 | 12.2.3, 12.0, 11.5, 11.2, 11.0 | Touchstone 2025 (13.0) | When running an analysis and saving by peril, losses in the Summary EP table will be grouped into peril plus sub-perils (e.g. 'EQ,FF,LS,SL,TS') for models that support sub-perils and by main peril only (e.g. 'EQ') for models that do not support sub-perils. |
| 396 | 5/7/2024 | 11.5, 11.2, 11.0 | Touchstone 2024 (12.0) | For specific exposure scenarios NetOfPreCat losses in the ByEvent table can be incorrect. |
| 395 | 5/7/2024 | 12.2.3, 12.0, 11.5, 11.2, 11.0 | Touchstone 2025 (13.0) | Back-allocation of ByTreaty losses into more granular save-by tables (ByTreatyGeo, ByTreatyExposureAttribute, ByTreatyExposureAttributeGeo) can be incorrect. |
| 394 | 4/15/2024 | 11.5, 11.2, 11.0 | Touchstone 2024 (12.0) | When multiple contracts with CSL type limits (CSLAI, CSL100) are present in an exposure, losses from these contracts might be overstated. |
| 393 | 4/15/2024 | 11.5, 11.2, 11.0 | Touchstone 2024 (12.0) | Import may fail for certain exposure coding combinations where a user codes the exposure with Limit type as 'Limit by coverage (Code- C)' and further populates Limit A, Limit B, Limit C and Limit D but keeps Limit 1 and Limit 2 as blank. |
| 392 | 4/15/2024 | 11.5, 11.2, 11.0 | Touchstone 2024 (12.0) | Loss Modification factors do not apply on expected lines when the rules include a single peril or combination of more than one peril in the template with multi-peril coded exposure. |
| 391 | 4/15/2024 | 11.5 | Touchstone 2024 (12.0) | For detailed loss analysis with multiple treaties, certain tables may have missing losses and cause CLF/CLA generation to fail. |
| 390 | 4/15/2024 | 11.5, 11.2, 11.0 | Touchstone 2024 (12.0) | GetLossAnalysisSummaryResults in the API is throwing an exception when the peril filter is set to anything other than AllLicensedPerils. |
| 389 | 3/7/2024 | 11.5 | The installation verification exposure files contain locations that will not produce loss on user environments for the Verisk Earthquake Model for the Middle East and therefore losses will not match those provided with the installation verification results file for this model. | |
| 388 | 2/29/2024 | 11.5 | Touchstone 2024 (12.0) | For a very specific policy structure, where facultative is attached on layer and treaty is attached on contract, the analysis may fail with an access violation error. |
| 387 | 2/29/2024 | 11.5 | Under very specific exposure conditions of non-layered locations, with very high replacement value, and disaggregation applied with analysis run with the U.S. Severe Thunderstorm model for events where one of the perils has an extremely low damage ratio, the analysis may fail for specific events. | |
| 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. |
| 385 | 2/29/2024 | 11.5, 11.2, 10.0 | Touchstone 2024 | When an RE treaty or a facultative contract is attached on layer and the Treaty peril code is a sub-set of the layer peril code, then the layer Gross loss for the peril which is not covered by the treaty is not included in final contract Gross and Net. |
| 384 | 2/29/2024 | 11.5 | Touchstone 2024 | Min/Max NGM terms do not apply for Geospatial analysis with Workers' Compensation exposure. |
| 383 | 2/29/2024 | 11.5, 11.2, 11.0 | Touchstone 2024 | Long treaty names cause Export Treaty to CLA failures. |
| 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. |
| 381 | 1/17/2024 | 11.2, 11.0 | Touchstone 2023 (11.5) | In some situations treaties are taking losses from all LOBs / Areas instead of from filtered LOB/ Areas. |
| 380 | 1/17/2024 | 11.2, 11.0 | Touchstone 2023 (11.5) | For any onshore portfolio, if a user runs the detailed loss analysis with combined singles limit type and the exposure has other terms like 'Attachment point' then the limit type is not getting applied resulting in an incorrect gross loss. |
| 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. |
| 378 | 9/18/2023 | 11.2, 11.0 | Touchstone 2024 | For locations with minimum policy deductibles and location limits types coverage or site, the deductible is not being applied on ground-up loss. |
| 377 | 9/18/2023 | 11.2 | Touchstone 2024 | For analyses run with the Verisk Earthquake Model for Japan and disaggregation enabled, the disaggregate location policy terms are not applied to the disaggregated location ground-up loss for a subset of events. |
| 376 | 9/18/2023 | 13.0, 12.0, 11.5, 11.2, 11.0 | Future Verisk Synergy Studio release | Reinsurance treaties with location target types are not getting applied to the locations in non-layered contracts. |
| 375 | 8/30/2023 | 11.2, 11.0 | Touchstone 2024 | Incorrect gross losses are produced when exposures with multi-peril terms and sub-limits have disaggregation applied. |
| 373 | 7/28/2023 | 11.2, 11.0 | Touchstone 2024 (12.0) | Loss analyses will fail when they have been submitted using loss analysis templates that were created in versions prior to Touchstone 2021 and saved as the default template. |
| 372 | 7/28/2023 | 11.2, 11.0 | Touchstone 2024 | Marine construction/occupancy pairs which do not produce loss are not included in the detailed analysis logs. |
| 371 | 7/28/2023 | 11.0 | Loss Modification analyses sometimes fail when the template contains a mix of exposure and event-based rules. | |
| 369 | 6/15/2023 | 11.2, 11.0 | Touchstone 2023 (11.5) | Demand surge will not be applied in the Verisk Typhoon Model for Southeast Asia when the analyzed exposure contains locations within the domain of one of the other models in the Pacific Basin. |
| 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. |
| 367 | 6/15/2023 | 11.2, 11.0 | Touchstone 2024 | Detailed loss analyses will not complete when applying a rule based event filter to the previous version of the Verisk Earthquake Model for Hawaii. This issue does not affect v3.10 of the model contained in the current event sets. |
| 366 | 6/15/2023 | 12.2.3, 11.2, 11.0 | Touchstone 2023 (11.5) | LLEI Hazard analyses are failing for models which are part of umbrella models and for which Prior Model Versions (PMV) have been removed. For example: LLEI is failing with the Tropical Cyclone peril for U.S. and Caribbean locations. |
| 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. |
| 364 | 6/15/2023 | 11.0 | Touchstone 11.2 Service Pack | Detailed loss numbers are incorrect for Japan Personal Accident analyses which have been saved by location counts (claims, injury or MAOL), where disaggregation is turned on, and where the analysis has been saved by some Geography. |
| 363 | 6/15/2023 | 11.0 | Touchstone 11.2 Service Pack | Incorrect Location Summary gross losses are being generated where exposure has Location or Spot facultative reinsurance and the analysis is saved by Location Summary. |
| 362 | 6/15/2023 | 11.2, 11.0 | Touchstone 2023 (11.5) | Differences in loss output between Net values for Geography and Contract or Event total are seen for analyses where there is commercial exposure, the Net of Pre-CAT perspective is selected and the analysis options include saving by some geographic resolution. |
| 361 | 6/15/2023 | 11.0 | Touchstone 11.2 Service Pack | When running a loss analysis using the Verisk Earthquake Model for Mainland China and saving by Line of Business and Subarea, different ground up loss numbers will be generated in the event level and exposure attribute by geography tables. |
| 360 | 6/15/2023 | 11.2, 11.0 | Touchstone 2023 (11.5) | Treaties are not applied in Workers' Compensation loss analyses which are saved by layer, event total, zone, and location summary. |
| 359 | 6/15/2023 | 11.2, 11.0 | Touchstone 2023 (11.5) | Under certain circumstances, gross coverage losses are changed in the ByEvent table when Extra Expense limits are used and the analysis is saved by location summary. |
| 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. |
| 357 | 6/15/2023 | 11.0 | Touchstone 11.2 Service Pack | In situations where a detailed loss analysis is running and a compute node becomes unavailable, for some reason, the analyses will fail. |
| 356 | 6/15/2023 | 11.2, 11.0 | Touchstone 2023 (11.5) | Loss analysis output may be incorrect under a specific set of circumstances where locations are coded for parent perils, there is a sub-peril sublimit, and given events do not produce loss for that subperil when the analysis is run by one or more subperils. |
| 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. |
| 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. |
| 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. | |
| 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. | |
| 306 | 8/5/2020 | 11.2, 11.0, 9.1, 9.0 | Touchstone 2021 | When exporting to Unicede, Insured Values are mistakenly doubled for earthquake exposure coded as PAL. |
| 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. | |
| 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 |