[bug] Workflow can be started even if there is an error in the Script component, and execution history is empty

[monikakuster]

When a workflow contains a Script component with a syntax or other error, the workflow can still be started.

After starting:

• The workflow status is "failed", but the execution history is empty (no steps are shown).

• From the execution view, it is impossible to determine where the error occurred.

• Only when opening the code editor for the Script component does the error message become visible.

• The backend application logs show a stacktrace with an IllegalArgumentException (e.g., due to an invalid expression).

Log:

2026-03-09T11:00:47.736+01:00 ERROR 431771 --- [server-app] [cat-handler-410]  s.g.e.ExceptionResolversExceptionHandler   : Unresolved IllegalArgumentException for executionId 7f0259d9-038f-99f4-c68e-43d84677abf7

java.lang.IllegalArgumentException: Invalid expression: function perform(input, context) {
	let message= 'Zaprimljeni su sljedeći računi:<br><br>'
	var sviRacuni = input.sviRacuni;


	for (let i = 0; i < sviRacuni.length; i++) {
		message += `Račun ${i+1}: <br>`
		message += sviRacuni[i];
		message += `<br><br>`;
}

	return message;
}
	at com.bytechef.evaluator.SpelEvaluator.evaluate(SpelEvaluator.java:221)
	at com.bytechef.evaluator.SpelEvaluator.evaluateInternal(SpelEvaluator.java:262)
	at com.bytechef.evaluator.SpelEvaluator.evaluate(SpelEvaluator.java:252)
	at com.bytechef.evaluator.SpelEvaluator.evaluateInternal(SpelEvaluator.java:262)
	at com.bytechef.evaluator.SpelEvaluator.evaluate(SpelEvaluator.java:155)
	at com.bytechef.atlas.configuration.domain.WorkflowTask.evaluateParameters(WorkflowTask.java:111)
	at com.bytechef.platform.configuration.facade.WorkflowNodeScriptFacadeImpl.getWorkflowNodeScriptInput(WorkflowNodeScriptFacadeImpl.java:164)
	at com.bytechef.platform.configuration.web.graphql.WorkflowNodeScriptGraphQlController.workflowNodeScriptInput(WorkflowNodeScriptGraphQlController.java:76)

Expected behavior:

• The workflow should validate the Script component before execution and prevent starting if there is an error.

• If an error occurs during execution, the execution history should clearly indicate where the error happened (component name and detailed message).

• The user should immediately see the cause of the error without having to manually open the Script editor or check backend logs.

script.json

Screencast.from.2026-03-09.10-54-32.webm