Conga Advantage Platform sends an email alert to workflow owners and administrators when a workflow or service hooks execution fails. This allows your team to identify and resolve issues before they cause broader disruption to business processes such as stuck approvals, missing record updates, or unprocessed actions.

A notification is sent when any of the following execution failures occur. Each failure type has a distinct cause, and understanding the difference helps you investigate and resolve it faster.

Failure scenario	What it means	Where to start
Workflow failed due to feedback loop detection	Conga Advantage Platform detected that the workflow was triggering itself or another workflow in a continuous loop and stopped the execution to protect system stability.	Review the trigger conditions for the affected workflow. Broad or poorly scoped conditions are the most common cause.
Workflow failed due to loop detection	Conga Advantage Platform detected a loop condition during execution and stopped the workflow before it could cause further impact.	Check for circular dependencies between workflows that operate on the same objects.
Workflow execution faulted	A general runtime error occurred during workflow execution. This is not related to a loop and may indicate a configuration issue or a problem with the record data at the time of execution.	Review the workflow configuration and check the execution log for the affected record to identify the specific error.
Service hooks execution failed due to feedback loop detection	Conga Advantage Platform detected a feedback loop involving a service hooks execution and stopped it to protect system stability.	Review the service hooks trigger configuration and check whether it interacts with any workflows on the same object.

For more information on designing safe triggers and preventing feedback loops, see Workflow and Service Hooks Trigger Best Practices.

When this feature is enabled, Conga configures the recipient list based on your organization's requirements. You can send notifications to individual users, user groups, or specific roles such as the workflow owner. This ensures that the appropriate recipients are alerted for each type of failure.

The following table describes how Conga Advantage Platform handles common recipient scenarios:

Scenario	Behavior
A user is configured as an individual recipient	The user receives one email notification.
A user group is configured as a recipient	All active members of the group receive an email notification.
A user appears both individually and as part of a configured group	The user receives only one email. The system prevents duplicate notifications automatically.
A user account is inactive	No notification is sent to that account. Inactive users are excluded automatically.