Camunda人工任务Create事件监听器Groovy脚本设变量报错求助

Hey there, let's figure out why you're running into this error when trying to set a process variable in a manual task's Create event listener, and walk through fixes that should resolve it.

Possible Causes & Solutions #

1. Timing Issues with the Create Event #

The Create event for a manual task fires right as the task is being created, before it's fully persisted to the Camunda database. At this point, the execution context might not be fully stabilized, which is why the system throws an error saying the task/process instance isn't available.

2. Use the Task Object to Access Execution (Instead of Direct Execution) #

Instead of calling execution.setVariable() directly, try fetching the execution from the task object first—this ensures you're working with a fully initialized execution context:

// Get the execution instance tied to the task
def processExecution = task.getExecution();
// Set the variable using this valid execution reference
processExecution.setVariable('newUserType', "RMAOFF1");

If the variable only needs to be tied to the specific task (not the entire process), you can also set a task-local variable first, then sync it to the process variable if needed:

// Set task-local variable first
task.setVariableLocal('newUserType', "RMAOFF1");
// Sync to process variable if required
task.getExecution().setVariable('newUserType', task.getVariableLocal('newUserType'));

3. Switch to the Assignment Event Type #

If you don't strictly need to set the variable the moment the task is created, use the Assignment event listener instead. This event fires after the task has been fully created and assigned to a user/group, so the task and process instance are fully persisted and stable. This is often a more reliable spot for process variable updates.

4. Check for Camunda Version Bugs or Configuration Conflicts #

Older Camunda versions had known issues with execution context availability in Create event listeners. If the above fixes don't work, verify your Camunda version—consider upgrading to a recent stable release if you're on an older one. Also, check your process definition for conflicting async tasks or other listeners that might be interfering with the process instance state.

5. Enable Debug Logging for Deeper Diagnosis #

Turn on Camunda's debug logging for the org.camunda.bpm.engine.task and org.camunda.bpm.engine.execution packages. This will give you a step-by-step view of how the task is created and how the execution context is handled, helping you pinpoint exactly where the failure occurs.

内容的提问来源于stack exchange，提问作者mandar