Inkcite’s Failsafes ensure your email includes everything you want and nothing you don’t. Out of the box, Inkcite automatically warns you if your current project meets any of these conditions:
Inkcite also supports custom Failsafes. These allow you to verify that your email either includes or excludes specific content.
For example, let’s say your company’s authorized resellers were formerly called “dealers”, but now must always be referred to as “retailers” instead. Additionally, every email you create must include a link allowing the recipient to find a local retailer. These are the sort of requirements that Failsafes were made for.
When a Failsafe is triggered, Inkcite will warn you in its command line output:
You can specify as many Failsafes as necessary, and they can be defined globally and/or by environment.
Viewing your email locally and sending preview versions still work when Inkcite detects problems in your email, but you can’t build the production assets unless you force Inkcite to do it (not recommended).