Hi Everyone & Ironclad Product Team,
To raise awareness and gather input from other admins, I’m also posting this note in the Community section to crowdsource solutions and hear how others are handling this and I'm submitting a similar post it to the Ideas section as well to formally raise this as a feature request for your consideration.
I’d like to suggest an enhancement to Ironclad that would make it easier for administrators to identify the root cause of document generation failures—specifically when the system returns the error message: “No document to preview because none of the document conditions are met.”
In its current state, diagnosing this issue can be extremely difficult, especially in complex workflows with multiple conditional logic layers created by another team member. When templates, properties, and conditions are interdependent and undocumented, it becomes a time-consuming process to analyze legacy logic, update configurations, and ensure documents generate properly—often requiring extensive trial and error just to pinpoint which condition isn’t being met.
It would be tremendously helpful if Ironclad could provide clearer diagnostics or an admin-facing debug tool to identify which condition(s) are not being met when this error occurs. Even a basic summary indicating which document templates were evaluated and which conditions failed would significantly improve troubleshooting efficiency.
Thank you for your time and for continuing to improve the admin experience. I’d be happy to provide additional context if helpful.
Best,
Isis
