| EventCode | Context | EventMessage | Description / Solution |
|---|
| Task; Workflow | Multi Purpose Code logging in the context of a task | Multi Purpose code for several info logs around a task.
Also important in Context of workflow. |
| Job; Workflow | Multi Purpose Code logging in the context of jobs (task user association) | Multi Purpose Code logging in the context of jobs (task user association)
Also important in Context of workflow. |
| Workflow only | Multi Purpose Code logging in the context of pure workflow processing | Multi Purpose Code logging in the context of workflow processing |
| Task | The task can not be removed due it is used by a user. | One user has opened the task for reading or editing the task. Therefore this task can not be deleted. |
| Task | The task can not be removed due it is locked by a user. | One user has opened the task for editing the task, or some other action has locked the task.
Therefore this task can not be deleted. |
| Task | The task can not be locked for deletion. | The task must be locked by the deleting user, before it can be deleted. This lock could not be set. |
| Task; ManualStatusCheck Plug-In | The Task can not be set to finished, since not all segments have a set status. | Each segment must have set a status in order to finish the task. |
| Task | The current task status does not allow that action. | This error occurs if the current status of the task does not allow the triggering action. |
| Task; ArchiveTaskBeforeDelete Plug-In | Task could not be locked for archiving, stopping therefore the delete call. | The task must be locked by the deleting user, before it can be deleted. This lock could not be set. |
| Task | The referenced customer does not exist (anymore). | The user tried to add a non existence client to a task. Probably the customer was deleted in the mean time. |
| Task | Task usageMode can only be modified, if no user is assigned to the task. | Remove first all assigned users from the task, change the usage mode and reassign the users again. |
| Workflow only | Workflow Action: JSON Parameters for workflow action call could not be parsed with message: {msg} | Check the parameters field of the mentioned action in the additional log data, it can not be parsed as JSON. |
| Workflow User Preferences | The referenced user is not associated to the task or does event not exist anymore. | Reload the task properties. |
| Workflow User Preferences | Missing workflow step in given data. | Missing workflow step in given data. |
| Workflow User Preferences | Missing workflow step in given data. | Missing workflow step in given data. |
| Task; Workflow | The targetDeliveryDate for the task is deprecated. Use the LEK_taskUserAssoc deadlineDate instead. | Temporary warning for the task targetDeliveryDate (delivery date) api field. Deadline date should be defined on user- task-assoc level. |
| Task reference files | A non existent reference file "{file}" was requested. | The requested file does not exist on the disk. Either this was a malicious file request, or some one deleted the files on the disk manually. |
| Task | TaskType not valid. | Check the parameter given as taskType. |
| Workflow Manager | Workflow to class "{className}" not found! | In the application a not existent worfklow class was requested. This is probably a programming error. |
| Workflow Manager | Workflow with ID "{workflowId}" not found! | There is a task configured with a not (anymore) existent workflow. |
| Workflow Manager | {className}::$labels has to much / or missing labels! | The translatable labels of the the requested workflow do not cover all or to much strings of the workflow. |
| Project/Task | Missing projectId parameter in the delete project request. | In the delete project request the project id was not provided. |
| Task/User | The format of the segmentrange that is assigned to the user is not valid. Example: 1-3,5,8-9 | Check the input for the editable segments; must be like: "1-3,5,8-9". |
| Task/User | The content of the segmentrange that is assigned to the user is not valid. | Make sure that the values are not reverse and do not overlap (neither in itself nor with other users of the same role). |