Class AsyncAgentInvokeJobHandler

java.lang.Object

com.flowable.agent.engine.impl.job.AbstractAgentJobHandler

com.flowable.agent.engine.impl.job.AsyncAgentInvokeJobHandler

All Implemented Interfaces:

org.flowable.job.service.impl.nontx.NonTransactionalJobHandler<AbstractAgentJobHandler.AgentJobHandlerResult>, org.flowable.job.service.JobHandler

public class AsyncAgentInvokeJobHandler
extends AbstractAgentJobHandler

Author:

Filip Hrisafov

Nested Class Summary

Nested classes/interfaces inherited from class AbstractAgentJobHandler

AbstractAgentJobHandler.AgentJobHandlerResult

Field Summary

Fields

Modifier and Type	Field	Description
static final String	TYPE

Fields inherited from class AbstractAgentJobHandler

agentEngineConfiguration, logger

Constructor Summary

Constructors

Constructor	Description
AsyncAgentInvokeJobHandler(AgentEngineConfiguration agentEngineConfiguration)

Method Summary

Modifier and Type	Method	Description
void	afterExecute(org.flowable.job.service.impl.persistence.entity.JobEntity job, String configuration, AbstractAgentJobHandler.AgentJobHandlerResult agentJobHandlerResult, org.flowable.common.engine.impl.interceptor.CommandContext commandContext)
String	getType()
protected AbstractAgentJobHandler.AgentJobHandlerResult	handleGuardrailViolation(AgentInvocationContext agentInvocationContext, FlowableGuardrailViolationException ex, IntentEvaluationTrigger intentEvaluationTrigger, tools.jackson.databind.JsonNode jobConfiguration)	Invoked when the agent invocation (which runs in the non-transactional phase of the job) raises a guardrail business error.
protected void	propagateGuardrailViolationToCallback(AgentInstanceEntity agentInstance, FlowableGuardrailViolationException ex, org.flowable.common.engine.impl.interceptor.CommandContext commandContext)	Routes a guardrail business error raised by the asynchronous agent invocation to the waiting process/case, so it can be caught by a BPMN error boundary event or a CMMN fault sentry (mirroring what happens synchronously).

Methods inherited from class AbstractAgentJobHandler

auditExchange, execute, executeNonTransactionally, getAgentInvocationContextJson, getIntentEvaluationTrigger, invokeAgent

Methods inherited from class Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Details

TYPE

public static final String TYPE

See Also:

• Constant Field Values

Constructor Details

AsyncAgentInvokeJobHandler

public AsyncAgentInvokeJobHandler(AgentEngineConfiguration agentEngineConfiguration)

Method Details

getType

public String getType()

handleGuardrailViolation

protected AbstractAgentJobHandler.AgentJobHandlerResult handleGuardrailViolation(AgentInvocationContext agentInvocationContext,
 FlowableGuardrailViolationException ex,
 IntentEvaluationTrigger intentEvaluationTrigger,
 tools.jackson.databind.JsonNode jobConfiguration)

Description copied from class: AbstractAgentJobHandler

Invoked when the agent invocation (which runs in the non-transactional phase of the job) raises a guardrail business error. The default behaviour simply re-throws, subclasses can override to handle the error differently.

Overrides:

handleGuardrailViolation in class AbstractAgentJobHandler

afterExecute

public void afterExecute(org.flowable.job.service.impl.persistence.entity.JobEntity job,
 String configuration,
 AbstractAgentJobHandler.AgentJobHandlerResult agentJobHandlerResult,
 org.flowable.common.engine.impl.interceptor.CommandContext commandContext)

Specified by:

afterExecute in interface org.flowable.job.service.impl.nontx.NonTransactionalJobHandler<AbstractAgentJobHandler.AgentJobHandlerResult>

Specified by:

afterExecute in class AbstractAgentJobHandler

propagateGuardrailViolationToCallback

protected void propagateGuardrailViolationToCallback(AgentInstanceEntity agentInstance,
 FlowableGuardrailViolationException ex,
 org.flowable.common.engine.impl.interceptor.CommandContext commandContext)

Routes a guardrail business error raised by the asynchronous agent invocation to the waiting process/case, so it can be caught by a BPMN error boundary event or a CMMN fault sentry (mirroring what happens synchronously). This is the error-path counterpart of AgentUtil.handleAgentInstanceCallback(AgentInstance, AgentInvocationResult, CommandContext): the agent invocation ran in the non-transactional phase of the job, so the error cannot be propagated on the original stack and must be re-injected into the parent scope here, in a transaction. If nothing catches it, the propagation throws and the job fails (retry / dead-letter).