actions_execution_failed

Execution of an Action failed

client_name · string · required

Client name associated with the client_id, when available. May be empty string.

description · string · required

Description of the event. This can also contain a description of the issue for failure logs.

details · object · required

Log details

Show child attributes

environment_name · string · required

The name of the environment where the event occurred

Examples:

"prod-eu-1"

"prod-us-1"

hostname · string · required

The hostname associated with the request. For forwarded requests, this should resolve to the original hostname. For failure logs, this may include invalid hostnames.

ip · string<ipv4> string<ipv6> · required

The IP address associated with the request. For an auth related log this should be the end user IP. For a machine-to-machine auth flow this should be the IP of the computer doing the authentication. For management logs like sapi and mgmt_api_read this should be the IP of the admin using the manage dashboard.

log_id · string · required

Log id

strategy · string · required

Strategy of the connection in connection_id, when applicable and valid. This may be empty string.

Example:

["auth0", "waad", "oktawic", "google-oauth2"]

strategy_type · string · required

Category of the strategy in strategy, when applicable. This may be empty string.

Example:

["database", "social", "enterprise"]

tenant_name · string · required

Tenant name

type · string · required

Execution of an Action failed

Allowed value: "actions_execution_failed"

$event_schema · object

Event schema meta

Show child attributes

client_id · string | null

Client related to the API call. Clients are also called applications. The underlying application may not be owned by your tenant and may not be accessible. For failure logs, this may be a valid ID, an invalid one, or any ID.

connection · string

Name of the connection, when available. The connection here matches the connection_id field.

connection_id · string

ID of the connection on which the auth flow is happening or connection of the user doing the action, when applicable. For failure logs this field may contain an invalid ID.

date · string

The date when the event occurred in ISO 8601 format

Example:

"2024-01-15T10:30:00.000Z"

identity_user_id · string

ID for the user as reported by the IdP.

is_mobile · boolean

Whether the request originated from a mobile device. Only present when user_agent is available.

organization_id · string

ID of the organization related to this auth flow or action, when applicable. For failure logs, the value may be a valid ID, and invalid ID, or any other string.

organization_name · string

Name of the organization in organization_id, when applicable and valid. May be an empty string.

transaction_linking_id · string

Reflects the transaction linking ID provided at the start of the auth flow, if any. Only available when using decoupled authorization flows.

Pattern: ^[A-Za-z0-9-_]{27}$

user_agent · string

The user_agent behind this log, when available

Example:

"Chrome 120.0.0 / Mac OS X 10.15.7"

user_id · string

ID of the user behind the auth flow, or of the user executing the action, whichever applies. For machine to machine auth flows, this field may contain an empty string. For failure logs, the value may be a valid ID, an invalid ID, or empty string

user_name · string

Username of the user related to the ID is shown in user_id, when available. For failure logs, the value may be a valid username, an invalid username, or empty string.

Example:

["[e-mail]", "[phone]"]