Instance Errors
- Former user (Deleted)
When a workflow instance fails, errors are shown as “Task Errors” or “Internal Errors” in the Instances view and in the email sent reporting the failure. There will be one email for each error.
- 1 Error: Asset must have the same geometry type as defined in the form.
- 2 Error: The allocated team does not have the Accreditations necessary to service this job. Missing accreditations: [<accreditation>].
- 3 Error: The Details field is required if ShowDetailsTab on the Request Form is true.
- 4 Error: Can not evaluate condition: Can not evaluate left value
Error: Asset must have the same geometry type as defined in the form.
Connector: Asset, Create Asset
Cause: This will happen if the geometry type on the Asset form is not the same as the geometry type selected on Create Asset.
Why? In the Asset Form, the Geometry type is defined to be either Point, Line, or Polygon and this cannot be overridden when an Asset is created.
To Fix: Correct the Location Type on the Connector. Geometry Type of Point matches Geolocation. Geometry Type of Line and Polygon require Geometry.
If no assets exist already then you can change the geometry type on the form, but if assets exist already then the geometry type is fixed and cannot be changed.
Retry: If you are able to change the Asset Form then retry this task.
Connector Details
Form Definition
Error: The allocated team does not have the Accreditations necessary to service this job. Missing accreditations: [<accreditation>].
Connector: Job, Create Job
Cause: This will happen we use Allocate Job (on Create Job) to a particular team, but the team does not have the necessary accreditations (qualifications) as specified in the Job Template.
Why? The Job Template can define prerequisites for a team to do a job, covering both equipment and accreditations. If a team does not have the right equipment then this can be overridden, but they are lacking the right accreditations then the job cannot be assigned.
To Fix: In the “Create Job” node, either
(a) switch the Job Allocation from “Allocate Team” to either “No Assignment” or “Automate Allocation” and this will stop the problem from happening in the future, or
(b) change the allocated team to one that does have the correct prerequisites, which again will fix it for the future, or
(c) update the team members' accreditations so that the team does meet the prerequisite.
Retry: If you are able to change the team members' accreditations then you can Retry. If you change team allocation type then Retrying won’t make any difference as the changes will not be applied to existing Instances - this workflow will be broken and you will need to manage the rest manually.
Error: The Details field is required if ShowDetailsTab on the Request Form is true.
Connector: Request, Create Request
Cause: This will happen if you turn on “Job Details” on a Create Request connector, when the Form Definition for the Request does not have “Show Details Tab” turned on.
Why? Turning on Job Details on the connector should be used if you want to copy the job fields such as duration, start and stop, from the request to a job. But if you don’t have “Show Details” turned on, then the user will never enter the details into the request, and there won’t be anything to copy.
To Fix: Either turn off “Job Details” or turn on “Show Details Tab”. The screenshots below show both turned on.
Retry: If you can change the Request form to turn Show Details Tab on then Retry this task.
Connector Details
Form Definition
Error: Can not evaluate condition: Can not evaluate left value
Connector: Exclusive Branch
Cause: When an Exclusive Branch condition was evaluated the “1st Value” parameter is missing.
Why? This may be for a number of reasons. If you using a field in a form (as we are doing in the screenshot on the right) it could be:
You have set up the condition and then changed the asset/job/request node on which it was based to use a different form.
The field has not been filled in by the field worker - is it mandatory?
The condition has been tested before a field worker has had a chance to update the asset/job/request. This will occur if you are missing an Asset/Job/Request Status Changed connector.
To Fix: Have a look at the branch condition that has failed and see if you can work out what the problem is from the points above. Change the branch condition accordingly. If you can’t work it out you can select “Reset” for the “1st Value” and set it up again. Sometimes when you do it again you will notice something different and pick up the error.
Retry: If all you do is change the Workflow definition then Retrying won’t make any difference as the changes will not be applied to existing Instances. If you change something elsewhere in Gruntify it is worth retrying.