Skip to main content
The migration.hook_failed event is triggered when Prelude calls your migration hook and the call cannot be completed successfully. Use this event to monitor the health of your migration endpoint and alert on outages or misconfiguration.

Failure reasons

The reason field identifies the precise rule that failed. It is one of the following values:

Transport-level

Response-level

The following reasons are emitted when the hook returns 200 but the body does not match the expected response schema:

Event payload

Emitted when Prelude calls your migration hook and the call cannot be completed successfully.

reason
enum<string>
required

The reason the migration hook call failed. Transport-level reasons describe failures reaching the hook; response-level reasons describe failures validating the response body.

Available options:
request_failed,
invalid_status_code,
response_decode_failed,
missing_external_id,
missing_identifiers,
invalid_response
Example:

"missing_external_id"

occurred_at
string<date-time>
required
Example:

"2025-03-15T10:30:00Z"

dispatch_id
string
Example:

"123e4567-e89b-12d3-a456-426614174000"

correlation_id
string
Example:

"123e4567-e89b-12d3-a456-426614174000"