I don&#x27;t have a toy example offhand, but the resource failure case I mentioned is one. If resources A, B, and C are in flight at the same time and A fails, Terraform in some as-yet-undiagnosed circumstances will not record state changes caused by the still-in-progress work on B and C. This happens a lot with SNS queues, IIRC, because SNS queue operations on the AWS API take a relatively long time to resolve. So if, say, you mistyped an attribute for an EC2 instance, it can fail out and Terraform will happily forget that it created an SNS queue for you.<p>I have a sneaking hunch that the continuing problems with template-file resources (complaining that the &quot;rendered&quot; attribute doesn&#x27;t exist in dependent resources) are related to this, but can&#x27;t prove that; my clients don&#x27;t pay me to debug Terraform, but to get their stuff working, and that doesn&#x27;t leave much time to get in-depth with it now that I&#x27;ve decided not to use it for my own purposes anymore.