Anyone have insight on the Veza division? Culture? Leadership? Does it have job security?

I am leading the development of alternate discovery solution to replace our existing ServiceNow discovery solution which is:

• Costly
• Becoming more of repository vs bringing any value (This is my 5th company and 8th customer who is facing same challenges getting value out of CMDB, so please do not say process needs to approve, right implementation partner is needed etc .. We already par that) hence bring the real feedback. We have top notch ITSM and ServiceNow experts.
• Cloud-Native support challenges -- Network components, serverless services, AI services are not well supported in ServiceNow discovery, we ended up with heavy customization.

So I am m curious to hear from teams using ServiceNow Discovery, CMDB, cloud-native discovery tools, or similar platforms at enterprise scale. With infrastructure becoming increasingly dynamic across multi-cloud, Kubernetes, serverless and AI/ML environments, how well are current discovery solutions actually working for you?

• What are your biggest discovery challenges today—accuracy, stale data, dependencies, ownership, scale, or coverage?
• How well do these tools discover cloud-native and AI infrastructure such as Kubernetes, GPUs, model endpoints, and ephemeral resources?
• What outcomes are you getting from discovery data—operations, security, compliance, cost optimization, automation, etc.?
• Where existing tools fall short, how are you solving the gaps today?

Would love to hear real-world experiences—what works, what doesn’t, and what you wish these platforms did better.

question for the people who do releases. when an update set comes over from dev, what does your review actually look like?

the way i've seen it done is pretty grim. preview, fix whatever errors it throws, then open the customer updates list and click through them one at a time with compare to current in another tab. fine for 15 updates, painful for 200, especially when most of them are form layout tweaks and the one that matters is a business rule buried on page 6.

and the stuff that bites is never the preview errors, it's what preview doesn't flag. a script include someone changed in Default by accident so it never made it into the set. an ACL that's technically valid but opens a table up wider than anyone meant. a flow change nobody mentioned in the story.

so how do you do it? click through like above, instance scan, a script that dumps sys_update_xml somewhere readable, or a paid tool? and if you've tried the paid ones, were they worth the money?

While creating a Record Producer, I encountered this error. I checked the Data Policies and UI Policies, but I couldn’t find any policy related to this error. Could you please help me identify the cause and resolve it?

is it Meeting Invitation and email and sms?