Workflow builder error messages

The server.log file contains error messages that relate to the Workflow Builder.

No hit for workflow template

Log Type: Exception Header
INFO  (WFA:3340769 - 5712774 cstProvisionalBooking:27648718) No hit 
in cache for Workflow Template ID: 14313328. In order to get the cache 
current, restart your app server.
Resolution area
Workflow Builder
Issue
A workflow was retired but is still being called.
Suggested action
Find workflow by using the ID that is used in the metaschema: 
Select * from wf_lookup where wf_template_id='#####’;
Revise and publish the workflow.
Example
The Workflow Template ID indicates which workflow is being called.
INFO
[com.tririga.architecture.cache.WFCache]
(WFA:3340769 - 5712774 cstProvisionalBooking:27648718) No hit in cache 
for Workflow Template ID:  14313328. In order to get the cache current, 
restart your app server.

Workflow task error

Log Type: Exception Header
WARN Call workflow task encountered error.
Resolution area
Workflow Builder
Issue
A workflow does not exist or is not currently published.
Suggested action
Review the calling workflow and see whether the step is still necessary, or find out why the called workflow is missing. Make sure that the called workflow is currently published. Revise and republish the necessary workflows.
Example
Call workflow task encountered error. Task:  TaskStep:
 Call Workflow(38) WFTID=19118076.14 TSID=205820
 Label='Call a Subflow' EventAction='',
 Calling WF: ID: 19118075  Version: published, 
  Exception: com.tririga.platform.workflow.template.exception.
WFTemplateLoadingException:
  Problem loading Workflow Template for ID: 19118075 Version: 
published....
 Caused by: com.tririga.platform.workflow.template.exception.
WFTemplateNotFoundException:
  Workflow template not found in lookup table for ID: 19118075
...
  Caused by: org.springframework.dao.EmptyResultDataAccessException:
   Incorrect result size: expected 1, actual 0

Cannot reverse financial transaction

Log Type: Exception Header
WARN CANNOT REVERSE PREVIOUS TRANSACTIONS
Resolution area
Workflow Builder
Issue
An application is attempting to use the financial transaction function to reverse previous financial transactions. A financial reference object is not associated with the record, so the object is unable to find previous transactions to reverse.
Suggested action
Review the process and ensure that when the financial transaction is being processed it has a financial reference object.
Example
The financial transaction record 13119972 does not have a financial reference object.
WARN
[com.tririga.platform.finance.service.FinanceServiceImpl]
(WFA-2.5:1837189 - 13119943 De-Associate:14821223 IE=14821223)
CANNOT REVERSE PREVIOUS TRANSACTIONS:  This financial transaction, 
13119972, is not associated to an object so no previous transactions 
can be reversed.

Error evaluating condition expression

Log Type: Exception Header
WARN Error evaluating condition expression - returning FALSE.
Resolution area
Workflow Builder
Issue
Switch conditions cannot be loaded, because they are invalid.
Suggested action
Revise the workflow. Review and update the conditions. Republish the workflow.
Example
The workflow cstBidDocument - onChange - Update UOM has an invalid Switch condition.
WARN
[com.tririga.platform.workflow.runtime.condition.Condition]
Error evaluating condition expression - returning FALSE.
Condition[ID=55383,Expr='substring (p0 , 10 , 10 ) == "A" || 
substring (p1 , 10 , 10 ) == "H" || substring (p2 , 10 , 10 ) == "G" 
|| substring (p3 , 10 , 10 ) == "L"',Parameters=[p0 = , p1 = , p2 = , 
p3 = ]]. Workflow Info: WFTemplateImpl.WFTemplateRO[ID=18749944,
Version=2,Name=cstBidDocument - onChange - Update UOM], TaskStep: 
WFTaskStepImpl.WFTaskStepRO[135720,,Switch,14,
WFTemplateImpl.WFTemplateRO[ID=18749944,Version=2,
Name=cstBidDocument - onChange - Update UOM]][MID-739830450]

Mapping into target field not allowed

Log Type: Exception Header
Mapping into the target field is not allowed because the field is 
within a Live Link section.
Resolution area
Workflow Builder
Issue
A field is being mapped into a live link section. Only the section mapping is used for a live link section.
Suggested action
Revise the workflow, open the task, open the workflow map, clear the field map for the live link section, and save workflow map. Publish the workflow.
Example
Workflow ID 10014934 version 17 has an invalid section map to the Line Item Summary History business object for the RecordedBy section.
WARN
[com.tririga.platform.workflow.template.sofieldmap.MapEntry]
Mapping into the target field is not allowed because the field is 
within a Live Link section. 
The mapping is being discarded.MEFieldToField[MapEntry Field-to-Field,
Type=10,SrcField=1037,TgtField=1037,Map=SOFieldMapImpl.
SOFieldMapRO[ID=1968,WFTemplate=10014934.17]]. TARGET: 
BoFieldImpl[name=StateProv,id=1037,
Section=BoSectionImpl[name=RecordedBy,id=BoSectionId[categoryId=1,
subCategoryId=7],Business Object=BoImpl[name=Line Item Summary 
History,id=10000072,module=ModuleImpl[name=Line Item,id=27]]]]
[MID-3898920414]

Invalid locator metadata

Log Type: Exception Header
WARN Trouble setting the locator field because the locator metadata 
is invalid; setting with the linked object's name instead.
Resolution area
Data Modeler or Workflow Builder
Issue
The Data Modeler uses a field for a locator that is different than the field that is being mapped into the field in a workflow.
Suggested action
Review the field used in the Data Modeler for the locator to ensure the proper mapping. Update and republish the mapping. Locator fields are sometimes used for multi-object mappings, and this warning may be seen in this scenario and can be ignored.
Example
The Notification business object in the Mail module had a RefObject locator. The RefObject locator is mapped to the linked record name instead of the identified field from the Data Modeler. This warning can be ignored.
WARN
[com.tririga.platform.smartobject.domain.field.LocatorField]
(WFA-2.5:1837189 - 13119943 APPROVE_HIDDEN:14821226 IE=14821226)
Trouble setting the locator field because the locator metadata 
is invalid; setting with the linked object's name instead. 
Locator field: BoFieldImpl[name=RefObject,id=1021,
Section=BoSectionImpl[name=AdditionalDetail,
id=BoSectionId[categoryId=1,subCategoryId=6],
Business Object=BoImpl[name=Notification,id=107324,
module=ModuleImpl[name=Mail,id=17]]]][MID-1263122157]

Workflow SmartObject field mapping

Log Type: Exception Header
WARN Workflow SmartObject field mapping.
Resolution area
Workflow Builder
Issue
A field or section in a workflow field mapping does not exist in the underlying business object.
Suggested action
Revise the workflow. Open the task. Open, review, and save the workflow map. Publish the workflow.
Example
Workflow ID 10328588 version 3, task Modify Records, has an invalid section map for the Team Members section into the Capital Project business object in the Project module.
WARN
[com.tririga.platform.workflow.template.sofieldmap.SOFieldMapImpl]
Workflow SmartObject field mapping.
MEObjectToSection[MapEntry Object-to-Section,Type=30,
TgtSectionCatagory=12,TgtSectionSubCatagory=1,TgtField=1,
Map=SOFieldMapImpl.SOFieldMapRO[ID=10853,WFTemplate=10328588.3]]. 
Mapping FROM: BoImpl[name=External Contact,id=106849,
module=ModuleImpl[name=People,id=7]],  
TO: BoImpl[name=Capital Project,id=107010,
module=ModuleImpl[name=Project,id=19]].  
TaskStep: Modify Records(28) WFTID=10328588.3 TSID=133061 
Label='Modify Records' EventAction='Append'. 
Cause: com.tririga.platform.metadata.MetadataNotFoundException: 
No section with name 'Team Members' exists on this Business Object: 
BoImpl[name=Capital Project,id=107010,
module=ModuleImpl[name=Project,id=19]][MID-3776864463]

Workflow task handler error

Log Type: Exception Header
WARN Workflow task handler error while triggering action
Resolution area
Workflow Builder
Issue
A state transition is performed that is not valid for the current state of the record on which the workflow is running.
Suggested action
Review the business object in question and check that the action or transition is still there. If the state transition is not there, you can add the state transition, and revise and republish the business object. If the state transition is there, the workflow might be called on a record that is not in an appropriate state for this transition to occur. Review your processes to ensure that records are in the proper state before the workflow runs.
Example
In the xxx workflow, the cstCalculateEnd task, the workflow is trying to run the cstCalculateEnd state transition. The cstCalculateEnd state transition is not a valid transition from the current state of the record.
WARN
Workflow task handler error while triggering action 'cstCalcuateEnd'.
TaskStep: Trigger Action(31) WFTID=16680680.10 TSID=138571 
Label='cstCalculateEnd' EventAction='cstCalcuateEnd'.
Cause: com.tririga.platform.metadata.MetadataNotFoundException:
No transition exists on this Business Object from current state
'BoStateImpl[Name=triActive,Business 
Object=BoImpl[name=cstTimeCalculator,id=10005047, 
module=ModuleImpl[name=triHelper,id=21720]]]'
with transition name of 'cstCalcuateEnd'.