When a stack creation fails, the error message does not include the failed resource name.
For example, see the following error message/stack trace;
{"explanation": "The server could not comply with the request since it is either malformed or otherwise incorrect.", "code": 400, "error": {"message": "{u'Error': u'Interval must be larger than Timeout'}", "traceback": "Traceback (most recent call last):\n\n File \"/opt/stack/heat/heat/engine/service.py\", line 63, in wrapped\n return func(self, ctx, *args, **kwargs)\n\n File \"/opt/stack/heat/heat/engine/service.py\", line 568, in create_stack\n stack.validate()\n\n File \"/opt/stack/heat/heat/engine/parser.py\", line 428, in validate\n raise StackValidationFailed(message=result)\n\nStackValidationFailed: {'Error': 'Interval must be larger than Timeout'}\n", "type": "StackValidationFailed"}, "title": "Bad Request"}
Including resource name in the error message helps in identifying the problem.
Note, this is about stack validation, not stack creation. Errors during the actual creation of a stack are always reported in context.