Hello again Mick Hansen, thanks again for your asnwer, i follow your advices but i don't know what is the problem, i leave you 2 codes to make an commit until email is ok, in resume it have to do: "first make a query in db to know If employee not exists in db so if this exists i send a note to the client using json with something like hey "There are an employee with this name", so if the user not exists in db i use the method of sequelize create to create de employee but the thing here is that i really don't want insert yet, i will insert it, but later, so imagine that i insert but the transaction is yet waiting for the t.commit(); using this logic i can get the id of employee and use later, at this point, i do a new query on db to check if exists an email with the value provided by form html, if the email exist i send a new response json telling hey "There are an employee with this email", if the email doesn't exists i proceed to create using again the method create of sequelize.

In resume the idea to use transactions is first pass al 4 validations an then commit if amid of all the caos occurs something bad i rollback the transaction and i will be happy, but not working, Sequelize in my opinion is the best framework to work with databases relationals like MySQL, PosgreSQL and SQLite and this point of transaction have a behavior weird or in better opinion seems like don't work like charm.
Another point is, i think you are an employee or something of the team Sequelize and iknow that i don't have to tell you everything about what i'm doing with this, and i tell you this because in the documentations there are 2 examples but 1 of those examples are bad, look this code:

If people run this code will throw an exception.
If you think that i'm wrong about the concepts of transaction tell me, i know that you also works, i don't want to be a headache for you also my english is not perfect because my language is spanish, so take me some patience thus as I have of you.
Thanks.