<p>Error 1360 indicates that a referenced trigger name cannot be found in the current MySQL schema.</p>
<p>MySQL Error 1360: ER_TRG_DOES_NOT_EXIST appears when a SQL statement refers to a trigger that is missing or was never created. Verify the trigger name and schema, then recreate or drop all references to resolve the issue.</p>
Trigger does not exist
The server raises ER_TRG_DOES_NOT_EXIST when a statement tries to alter, drop, or fire a trigger that the data dictionary cannot locate. The trigger may have been deleted, created in another schema, or never defined.
The error stops the current transaction because MySQL cannot execute operations tied to an unknown trigger. Fixing it quickly restores data integrity and application stability.
Developers see the error during ALTER TABLE, DROP TRIGGER, or INSERT/UPDATE actions that should invoke a missing BEFORE or AFTER trigger. It also appears in mysqldump restores if triggers were skipped.
CICD pipelines often surface the error while replaying migrations on new environments where the trigger script was not applied.
Missing triggers break business rules enforced at the database layer, causing silent data corruption. Eliminating the error ensures validation, auditing, and cascading logic run reliably.
Continuous integration workflows fail fast on this error, blocking deployments until the trigger definition is restored or dependencies are removed.
A simple typo in DROP TRIGGER or ALTER TABLE ... DROP/ADD TRIGGER statements leads MySQL to search for a non-existent trigger.
Executing trigger operations in the wrong schema makes valid trigger names invisible because MySQL looks only in the current database.
Deploying to staging or production without the CREATE TRIGGER script means later migrations reference a trigger that was never created.
An admin may have dropped the trigger to troubleshoot, forgetting to recreate it, leaving dependent code broken.
Restoring data only imports tables. Without the --triggers flag, trigger objects are skipped, so applications referencing them fail.
Occurs when a referenced table is missing. Similar root cause: object does not exist.
Triggered by missing parent tables or mismatched data types during constraint creation.
Raised when calling a stored procedure that is absent, paralleling the missing trigger scenario.
Yes. MySQL removes all triggers tied to a table when that table is dropped, which can later cause ER_TRG_DOES_NOT_EXIST if migrations assume the trigger persists.
Galaxy tracks and versions SQL migrations, letting teams confirm CREATE TRIGGER scripts run in every environment. Its AI copilot flags missing trigger references during code review.
No. MySQL stops the operation when the trigger is missing. You must recreate the trigger or remove the reference to continue.
All supported MySQL versions, including 5.7, 8.0, and MariaDB forks, emit error 1360 when a trigger is not found.
.avif)
.avif){kind=logo}
