Workflow errors with no way to track the issue



I've been using workflows a lot and right now I'm running into trouble using it.

I've setup a hierarchical structure of projects starting with a central project (called general) and many subprojects.

The target versions of epics are set in the general project and workflows will update those changes troughout all other projects up until the work items. This works very nicely, but at some point this stopped working.

The error I'm getting is

Workflow npf2-scrum-flow-toplevel reports error: Cannot resolve property Issue.Target version in project <noname>
Contact project admin X


As you can see, the system doesn't give me proper info on how to fix this. What is <noname>? Is it something that was cached?

I've analyzed the whole issue tree and every project has the Target version field defined with the same bundle (so the field and bundle match 100%). Still it's getting stuck somewhere.

Does anyone have any idea on how to debug this behavior?


Thanks a lot


I went digging in the log files I received from our IT department and this error is logged and most likely related. However, I cannot seem to pinpoint where this issue is coming from. It keeps talking about project <noname>.

In my workflow I iterate the subtasks of the issue and I set the target version to be equal to the current issue (so it cascades down). From the looks of it, the workflow is attempting to update an issue that hasn't got that field available, but I know for sure that every issue in every subproject has that field, unless there is some kind of hidden project where other issues are being evaluated from.


27 Mar 2017 11:05:01,886 ERROR [telessOnScheduleRule] [QuartzJobProcessor2                               ] [workflow_user_1911719630] Failed to execute action for issue 3AG-74
jetbrains.mps.webr.runtime.templateComponent.LocalizedLogicException: Workflow rule "npf2-scrum-flow-toplevel->SCH Cascade properties to subtasks schedule" threw an exception in project TripleA: General.
Cannot resolve property Issue.Target version in project <noname>.
Contact rule owner xxx (xxx) xxx@xxx for further information.
    at jetbrains.youtrack.workflow.model.Rule.wrapRuntimeException(
    at jetbrains.youtrack.workflow.model.StatelessRule.handle(
    at jetbrains.youtrack.workflow.model.StatelessOnScheduleRule$2$1$1.invoke(
    at jetbrains.youtrack.workflow.model.StatelessOnScheduleRule$2$1$1.invoke(
    at jetbrains.youtrack.workflow.model.StatelessOnScheduleRule.doUnit(
    at jetbrains.youtrack.workflow.model.StatelessOnScheduleRule$2$1.invoke(
    at jetbrains.youtrack.workflow.model.RhinoRuleLoader.runInContext(
    at jetbrains.youtrack.workflow.model.StatelessOnScheduleRule$2.invoke(
    at jetbrains.youtrack.workflow.model.StatelessOnScheduleRule.onCron(
    at jetbrains.youtrack.workflow.model.QuartzJobImpl$
    at jetbrains.mps.businessRules.runtime.TransactionalExecutor$1.invoke(
    at jetbrains.teamsys.dnq.runtime.txn._Txn.runNew(
    at jetbrains.mps.businessRules.runtime.TransactionalExecutor.execute(
    at webr.framework.controller.BeanContainerAwareExecutorWrapper.execute(
    at jetbrains.youtrack.workflow.model.QuartzJobImpl.execute(
    at jetbrains.exodus.core.execution.RunnableJob.execute(
    at jetbrains.exodus.core.execution.ThreadJobProcessor.executeJob(
    at jetbrains.exodus.core.execution.JobProcessorQueueAdapter.doExecuteJob(
    at jetbrains.exodus.core.execution.JobProcessorQueueAdapter.doJobs(
    at jetbrains.exodus.core.execution.ThreadJobProcessor$
Caused by: jetbrains.mps.webr.runtime.templateComponent.LocalizedLogicException: Cannot resolve property Issue.Target version in project <noname>
    at jetbrains.youtrack.workflow.wrappers.EntityWrapper.getPropertyValueResolver(
    at jetbrains.youtrack.workflow.wrappers.EntityWrapper.set(
    at sun.reflect.GeneratedMethodAccessor591.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(
    at java.lang.reflect.Method.invoke(
    at org.mozilla.javascript.MemberBox.invoke(
    at org.mozilla.javascript.ScriptRuntime.applyOrCall(
    at org.mozilla.javascript.BaseFunction.execIdCall(
    at org.mozilla.javascript.optimizer.OptRuntime.call2(
    at org.mozilla.javascript.gen.initialscript_js_400._c_anonymous_18(initialscript.js:133)
    at org.mozilla.javascript.optimizer.OptRuntime.callName(
    at org.mozilla.javascript.gen.npf2_scrum_flow_toplevel__SCH_Cascade_properties_to_subtasks_schedule_401._c_anonymous_2(npf2-scrum-flow-toplevel->SCH Cascade properties to subtasks schedule:8)
    at>SCH Cascade properties to subtasks schedule)
    at org.mozilla.javascript.ContextFactory.doTopCall(
    at org.mozilla.javascript.ScriptRuntime.doTopCall(
    at>SCH Cascade properties to subtasks schedule)
    at org.mozilla.javascript.JavaAdapter.doCall(
    at org.mozilla.javascript.JavaAdapter.callMethod(
    at adapter2.action(<adapter>)
    at jetbrains.youtrack.workflow.model.StatelessRule.handle(
    ... 23 more


Hello, I'm sorry for the delay.

Could you please check that the workflow 'SCH Cascade properties to subtasks schedule' is attached to all the projects where your subtasks belong?

Thank you.


Hello and sorry for the delay as well.

The issue with that is that I cannot do that. The workflow on the general project differs a little than the one on the child projects. The workflow in the general (top level) project is using a check on a type that doesn't exist in the child projects.

I have a similar rule in the workflow of the child projects but without that type check.

This worked fine for a long time until a certain point in time, something small must have changed to the project or any of the workflows. The problem is I cannot seem to find out what exactly is going wrong.


Small update, after testing again by enabling the rules I no longer have any issues.

Strange that this issue came and went without any changes in the workflows nor project structure. I just hope it doesn't return.

Thanks for the help though.


Please sign in to leave a comment.