https://community.telligent.com/community/14/Verint Community 14 significantly improves performance, efficiency, visibility, resiliency, and upgrading.en-US14.0.0.684 14https://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624045Wed, 14 Oct 2026 14:28:00 GMTforumreply:1624045Yes the compose file from How do I get started with installation? has the version (644) which appeared to work for Justin McCullagh after updating the search ver from 619 to 639 but not for me I also have a separate build from the dev example page which has 684 and 639 and that also shows the same error re searchhttps://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624044Wed, 14 Oct 2026 14:09:00 GMTforumreply:1624044It appears to are still running 644 and it should be 684 of communityhttps://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624042Wed, 14 Oct 2026 08:44:00 GMTforumreply:1624042Hi Patrick M. I started it again this morning As per Justin's comments I had changed the baseline compose file and updated, but it still shows the warning in the web monitoring as before Before I tear it down and try again another clean setup is there anything else we can checkhttps://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624041Tue, 13 Oct 2026 15:45:00 GMTforumreply:1624041The restart may have been the key, until the restart its possible that the community still thought the search was wrong. It would take some checking but that would explain why it seems code wise t be fine.https://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624040Tue, 13 Oct 2026 15:40:00 GMTforumreply:1624040Yes, it cleared after restart but I also removed the 619 image before my restart so it was just 639 that remained, not sure if that made a difference.https://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624039Tue, 13 Oct 2026 15:35:00 GMTforumreply:1624039To clarify, if you restart the containers does the issue on the schema go away?https://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624038Tue, 13 Oct 2026 15:04:00 GMTforumreply:1624038Yep, same schema status issue. Same for another dev here too. The initial yaml just has 619 in the setup docs, on clean setup its showing the issue from first start but updating to 639 and restart does fix ithttps://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624037Tue, 13 Oct 2026 14:31:00 GMTforumreply:1624037Do you get the schema status issue as well? So far in my review if you are running 639 then you should also not have that issue so its a bit perplexing unless its not truly updatedhttps://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624036Tue, 13 Oct 2026 13:00:00 GMTforumreply:1624036I had the same issue using the yaml in the setup docs How do I get started with installation? I had to update search to 14.0.0.639 manually to resolved the issuehttps://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624034Thu, 08 Oct 2026 21:55:00 GMTforumreply:1624034ok I will have to look at the other error, I had hoped you were just having a version mismatch but will look deeperhttps://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624033Thu, 08 Oct 2026 16:15:00 GMTforumreply:1624033Also tried a new clean 'dev' env install and this works but also still had the search error, which doesn't seem to stop search working in either set of builds D:\Dev\Community.14.Test\HelloCommunity\.devcontainer>docker compose pull [+] pull 38/38 ✔ Image af1.verintconnect.com/dfe-community/community/search:14.0.0.639 Pulled ✔ Image mcr.microsoft.com/mssql/server:2022-CU20-ubuntu-22.04 Pulled ✔ Image alpine:3.24.1 Pulled ✔ Image af1.verintconnect.com/dfe-community/community/infra:14.0.0.644 Pulled ✔ Image af1.verintconnect.com/dfe-community/community/web:14.0.0.684 Pulled ✔ Image af1.verintconnect.com/dfe-community/community/job:14.0.0.684 Pulled ✔ Image af1.verintconnect.com/dfe-community/community/installer:14.0.0.684 Pulled ✔ Image mcr.microsoft.com/dotnet/aspire-dashboard:13.6.0 Pulled ✔ Image axllent/mailpit:v1.27 Pulledhttps://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624032Thu, 08 Oct 2026 15:49:00 GMTforumreply:1624032There were 2 issues I can now pull down af1.verintconnect.com/dfe-community/community/search:14.0.0.639 so that should fix the issue with the plugin template asking for 639 which then didn't exist, thanks for that In my clean test env How do I get started with installation? I've updated search in there as a test from 619 to 639 F:\Docker\Community V14 Test\community>docker compose pull [+] pull 23/23 ✔ Image af1.verintconnect.com/dfe-community/community/installer:14.0.0.644 ✔ Image axllent/mailpit:v1.27 ✔ Image af1.verintconnect.com/dfe-community/community/infra:14.0.0.644 ✔ Image af1.verintconnect.com/dfe-community/community/search:14.0.0.639 ✔ Image mcr.microsoft.com/dotnet/aspire-dashboard:13.6.0 ✔ Image mcr.microsoft.com/mssql/server:2022-CU20-ubuntu-22.04 ✔ Image alpine:3.24.1 ✔ Image af1.verintconnect.com/dfe-community/community/job:14.0.0.644 ✔ Image af1.verintconnect.com/dfe-community/community/web:14.0.0.644 This still shows the search error,but not sure if this was what you meanthttps://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624031Thu, 08 Oct 2026 15:18:00 GMTforumreply:1624031Can you retry 14.0.0.639 and let me know if it works now?https://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624025Thu, 08 Oct 2026 13:55:00 GMTforumreply:1624025Thanks Patrick M.https://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624024Thu, 08 Oct 2026 13:54:00 GMTforumreply:1624024The community.telligent.com error I will look into, but it can be safely ignored, its a service that is just looking for product updates. I will look into the search issue. If this is development and you don't specifically need search you should be fine but it will still show the error. The newer image is an updated SOLR but not functionally different.https://community.telligent.com/community/14/f/ask-the-community/1152643/delegation-of-dns-control/1624023Thu, 08 Oct 2026 13:46:00 GMTforumreply:1624023More than likely you would have a single CNAME record(possibly an A record but not as common) that is creating and routing your subdomain to hosting. This record would be removed and replaced by an NS record with the name servers I mentioned that are provided.https://community.telligent.com/community/14/f/ask-the-community/1152643/delegation-of-dns-control/1624022Thu, 08 Oct 2026 13:36:00 GMTforumreply:1624022Hi, Thank you both for the info. I think I understand what you're saying, but our community is already a subdomain of our main website which is why I was trying to understand how this would work. I've asked my IT team if they have any issues with what you're suggesting and I'll update the thread when I've heard back.https://community.telligent.com/community/14/f/ask-the-community/1152643/delegation-of-dns-control/1624020Thu, 08 Oct 2026 13:32:00 GMTforumreply:1624020Thanks Patrick M. Liz Morgan You make a one-time update in your DNS, adding Nameserver (NS) records that delegate control of your community's subdomain (for example, community.companyname.com ) to Verint. Verint then manages everything behind that subdomain. Your root domain and all other DNS records stay fully under your control. Why it benefits you Less work for your IT team. After the initial setup, there are no DNS change tickets for routine platform updates, scaling, or maintenance. No expired-certificate outages. We can validate and renew your TLS certificates automatically, so your community never goes down because a cert lapsed. Faster response during incidents. If we need to fail over, re-route traffic, or put protection in front of the site (WAF, DDoS mitigation), we can act in minutes without waiting on a change window or an approval chain on your side. Smoother upgrades and migrations. Moving to new infrastructure, regions, or platform versions doesn't require a coordinated cutover with your network team. Better performance and availability. We can use health-checked records and geo- or latency-based routing to send your users to the best-performing endpoint. Stronger security hygiene. Because we own both the DNS records and the resources they point to, we can retire records when infrastructure changes, which prevents stale entries and subdomain takeover risk. Clear accountability. One party owns the stack from DNS to application, which makes troubleshooting faster and SLAs simpler. What stays with you Your root domain ( companyname.com ) and every other subdomain The ability to revoke the delegation at any time Visibility into changes, per our change-notification commitmentshttps://community.telligent.com/community/14/f/ask-the-community/1152643/delegation-of-dns-control/1624019Thu, 08 Oct 2026 13:12:00 GMTforumreply:1624019Upon initial setup of the site, we will provide the name servers names/IPs for a managed subdomain within our environment. For example, for acme.com with a community at community.acme.com, the subdomain community.acme.com will be managed inside of hosting. The provided name servers will need to be deployed to the root domain and after completion hosting will manage the subdomain for routing, ssl management, ssl domain verification, email identity verification and all items that require dns specifically for that subdomain. It does not change the root domain behavior and can always be revoked at the root domain.https://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624015Thu, 08 Oct 2026 11:15:00 GMTforumreply:1624015Looking at the compose file extracted from the template re Developing a Plugin it mentions newer versions of the images af1.verintconnect.com/dfe-community/community/web:14.0.0.684 af1.verintconnect.com/dfe-community/community/search:14.0.0.639 But the search artifact is not available for download Error response from daemon: failed to resolve reference "af1.verintconnect.com/dfe-community/community/search:14.0.0.639": af1.verintconnect.com/dfe-community/community/search:14.0.0.639: not found I checked the artifacts in jfrog and could only find one image for search (619), does 639 need to be published or the template updated? I realise I can update the compose file manually to use other older versions, raising this as it looks like they are out of sync at the moment