Errors
The page Errors shows all error jobs. So an error message always represents precisely one job and thus refers to exactly one profile.
See also: Sections Logging in Lobster_data and Error Handling.
(1) One or more errors can be handled via the context menu (right-click).
(2) Indicates whether an error job is locked and by which user. See also context menu below, item (1).
(3) Stacktrace of the selected error. Highlighted text can be copied with Ctrl+C. Note: If available, a trace file can be opened via a right-click and viewed on page Server Logs.
(4) If this option is set, errors will be displayed summed up per profile.
Context Menu
(1) An error (or several) can be locked under the name of the user. This prevents simultaneous processing of errors by several users. Note: See also function get unassigned errors.
(2) This opens another dialogue in which you can lock the error for a specific user (selectable from a list). You can also add a note that will appear in a pop-up when you point to the user in column Locked. Note: See also function get unassigned errors.
(3) Starts the selected job (or several or all) with the stored input data (backup) after a confirmation dialogue (without restart dialogue). See also system variable VAR_SYS_RESTART. Note: If the input data of this job no longer exists when it is restarted, this results in an error.
(4) Marked errors will be deleted from the error list. A confirmation dialogue will open. You can also specify a deletion reason. Note: The specification of a deletion reason can be forced with the option <Set name="remarkForDeletionRequired">true</Set> in configuration file ./etc/startup.xml.
Important note: The job is only deleted from the error list. It can still be found as an error in the job overview. The deletion reason you specified will be displayed at the end of the job log.
Note: The error page offers the possibility to handle errors centrally, but you still have a documentation of all errors and their corrections in the overview.
(5) The input file can be opened and edited in the editor and then saved or downloaded to the local computer.
(6) A locked error, which you have locked yourself (1), can be unlocked. If you have administrator rights, you can also force the unlocking if an error has been locked by another user.
(7) If an error is triggered by the function log user error(a,b,[c]), this option appears. The function can mark specific fields of the input data as faulty. In the Control Center, these errors can then directly be corrected in the input data in a special dialogue. Error jobs that have been flagged by this function are marked with an exclamation mark ! before the profile name. For details, please see the function description.
(8) Absolutely all errors are deleted (of all profiles and all clients).
(9) In a further dialogue, the job number, profile name and file name can be copied.