hibernate/hibernate-orm · error · EntityActionVetoException

Action was vetoed: ${entityAction}

Error message

Action was vetoed: ${entityAction}

What it means

Error "Action was vetoed: ${entityAction}" thrown in hibernate/hibernate-orm.

Source

Thrown at hibernate-core/src/main/java/org/hibernate/engine/spi/ActionQueueLegacy.java:314

			ACTION_LOGGER.executingIdentityInsertImmediately();
			execute( insert );
		}
		else {
			ACTION_LOGGER.addingResolvedNonEarlyInsertAction();
			OrderedActions.EntityInsertAction.ensureInitialized( this );
			insertions.add( insert );
		}
		if ( !insert.isVeto() ) {
			insert.makeEntityManaged();
			if ( unresolvedInsertions != null ) {
				for ( var resolvedAction :
						unresolvedInsertions.resolveDependentActions( insert.getInstance(), session ) ) {
					addResolvedEntityInsertAction( resolvedAction );
				}
			}
		}
		else {
			throw new EntityActionVetoException( insert );
		}
	}

	/**
	 * Adds an entity (IDENTITY) insert action
	 *
	 * @param action The action representing the entity insertion
	 */
	public void addAction(EntityIdentityInsertAction action) {
		ACTION_LOGGER.addingEntityIdentityInsertAction( action.getEntityName() );
		addInsertAction( action );
	}

	/**
	 * Adds an entity delete action
	 *
	 * @param action The action representing the entity deletion
	 */

View on GitHub (pinned to fad1729dce)

Solutions

1. Inspect the veto reason and resolve the conflicting queued action before re-executing
2. Avoid scheduling contradictory operations on the same entity within one flush

When it happens

Trigger: Thrown at hibernate-core/src/main/java/org/hibernate/engine/spi/ActionQueueLegacy.java:314 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of hibernate/hibernate-orm@fad1729dce (2026-08-22). Data as JSON: /api/errors/d690e9b138401858. Report an issue: GitHub.