Mysql Workbench - Error processing forward engineering - mysql

Question

I want to raise a small problem MySQL Workbench, but first of all I want you to know that this question previously made, but without much explanation and a lot of code that leaves many questions, and as I have not been to find the problem, the question will easy and explanatory possible.
1) I made a simple model in MySQL Workbench, a relationship between two tables.
If I make the execution "Forward engineering" of this model is created without problem.
But the problem it is following...
The code that generates me MySQL Workbench:
-- MySQL Workbench Forward Engineering
SET #OLD_UNIQUE_CHECKS=##UNIQUE_CHECKS, UNIQUE_CHECKS=0;
SET #OLD_FOREIGN_KEY_CHECKS=##FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0;
SET #OLD_SQL_MODE=##SQL_MODE, SQL_MODE='TRADITIONAL,ALLOW_INVALID_DATES';
-- -----------------------------------------------------
-- Schema example
-- -----------------------------------------------------
-- -----------------------------------------------------
-- Schema example
-- -----------------------------------------------------
CREATE SCHEMA IF NOT EXISTS `example` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci ;
USE `example` ;
-- -----------------------------------------------------
-- Table `example`.`status`
-- -----------------------------------------------------
CREATE TABLE IF NOT EXISTS `example`.`status` (
`id` INT UNSIGNED NOT NULL,
`name` VARCHAR(45) NULL,
`create_at` DATETIME NULL,
PRIMARY KEY (`id`))
ENGINE = InnoDB;
-- -----------------------------------------------------
-- Table `example`.`users`
-- -----------------------------------------------------
CREATE TABLE IF NOT EXISTS `example`.`users` (
`id` INT UNSIGNED NOT NULL AUTO_INCREMENT,
`name` VARCHAR(45) NULL,
`email` VARCHAR(45) NULL,
`password` VARCHAR(45) NULL,
`create_at` DATETIME NULL,
`status_id` INT UNSIGNED NOT NULL,
PRIMARY KEY (`id`),
INDEX `fk_users_status_idx` (`status_id` ASC),
CONSTRAINT `fk_users_status`
FOREIGN KEY (`status_id`)
REFERENCES `example`.`status` (`id`)
ON DELETE NO ACTION
ON UPDATE NO ACTION)
ENGINE = InnoDB;
SET SQL_MODE=#OLD_SQL_MODE;
SET FOREIGN_KEY_CHECKS=#OLD_FOREIGN_KEY_CHECKS;
SET UNIQUE_CHECKS=#OLD_UNIQUE_CHECKS;
2) I need to make an optimization to the table status, and I will make a simple change because the status.id only have a maximum of 10 records, and the data type INT id field think it's too big for this then what I would do is change id INT to id TINYINT
I made this simple change and stuck:
The code that generates me MySQL Workbench:
-- MySQL Workbench Forward Engineering
SET #OLD_UNIQUE_CHECKS=##UNIQUE_CHECKS, UNIQUE_CHECKS=0;
SET #OLD_FOREIGN_KEY_CHECKS=##FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0;
SET #OLD_SQL_MODE=##SQL_MODE, SQL_MODE='TRADITIONAL,ALLOW_INVALID_DATES';
-- -----------------------------------------------------
-- Schema example
-- -----------------------------------------------------
-- -----------------------------------------------------
-- Schema example
-- -----------------------------------------------------
CREATE SCHEMA IF NOT EXISTS `example` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci ;
USE `example` ;
-- -----------------------------------------------------
-- Table `example`.`status`
-- -----------------------------------------------------
CREATE TABLE IF NOT EXISTS `example`.`status` (
`id` TINYINT UNSIGNED NOT NULL,
`name` VARCHAR(45) NULL,
`create_at` DATETIME NULL,
PRIMARY KEY (`id`))
ENGINE = InnoDB;
-- -----------------------------------------------------
-- Table `example`.`users`
-- -----------------------------------------------------
CREATE TABLE IF NOT EXISTS `example`.`users` (
`id` INT UNSIGNED NOT NULL AUTO_INCREMENT,
`name` VARCHAR(45) NULL,
`email` VARCHAR(45) NULL,
`password` VARCHAR(45) NULL,
`create_at` DATETIME NULL,
`status_id` INT UNSIGNED NOT NULL,
PRIMARY KEY (`id`),
INDEX `fk_users_status_idx` (`status_id` ASC),
CONSTRAINT `fk_users_status`
FOREIGN KEY (`status_id`)
REFERENCES `example`.`status` (`id`)
ON DELETE NO ACTION
ON UPDATE NO ACTION)
ENGINE = InnoDB;
SET SQL_MODE=#OLD_SQL_MODE;
SET FOREIGN_KEY_CHECKS=#OLD_FOREIGN_KEY_CHECKS;
SET UNIQUE_CHECKS=#OLD_UNIQUE_CHECKS;
Error: If I make the execution "Forward engineering" of this model it shows me the following error:
I would greatly appreciate your help, thank you very much.