Log messages

Searching integration error messages, monitoring by batch, and attaching user-visible explanations to unmapped messages.

Log messages screen lists error messages generated by integration processes (such as invoice, cargo, ERP) and shows which explanation is displayed to the user for each message. Raw error texts from integrations are often technical and unclear; with mapping, a user-understandable explanation is attached to these texts. On this screen, you examine when, from which source, and in which process the error occurred; you can directly add a mapping to an unmapped message here. Support and operations teams monitoring integration errors use this screen.

Accessing the screen

  • Follow the menu path ComHub – Marketplace Integration › Error logs › Log messages.
  • The Logs with this error option in the row menu of a mapping on the Message mapping screen opens this screen filtered by that mapping's error message and source.

If you do not see it in the menu, your account does not have permission for this screen.

Screen sections

  • Title: Log messages.
  • Exact message filter (only when coming from Message mapping screen): a strip showing which message the list is filtered by.
  • Filter area: search box, date range, and additional filters; below are Clear, Detailed filters, and Filter buttons.
  • List: with Per page selection above, Filter result: [number] records text, refresh button, and Columns menu.
  • Note: explanation below the list reminding the default date range and sorting.
  • Message drawer: panel opening from the right when clicking a row.

Filtering and searching

Field Purpose Tip
Search Searches by expression in the message text. The box shows Text in message. Typing part of the message is sufficient.
Date range Filters by the day the message was generated. If left empty, the last 10 days (including tomorrow) are searched. Maximum range is 366 days.
Source Filters by the integration source producing the message. Default is All. Options are sources that actually appear in the selected date range.
Caller method Filters by the process where the message occurred. Default is All. Options are values appearing in the selected range.
Batch no Retrieves messages generated in the same batch process. The All messages of this batch button in the message drawer fills this field for you.
  • Filters apply when pressing the Filter button (or Enter in a field); if there are unapplied changes, Filter is highlighted. Clear resets the search box and all filters and immediately reloads the list; it does not remove the exact message filter (see below).
  • Source, Caller method, and Batch no are visible by default; you can hide them from the Detailed filters menu. The value of a hidden field is also cleared.
  • Source and Caller method options are generated based on the applied date range. Changing the date range and pressing Filter updates the options.

Exact message filter

When coming via the Logs with this error link on the Message mapping screen, an Only records exactly matching this message: strip with the message text appears above the list. Spaces in the message are shown with visible marks (· space, → tab, ↵ line end) because the match is exact including spaces. To remove this filter, press the Remove filter button on the strip; Clear does not remove this filter. The Source filter is also filled with the mapping's source when coming via the link; Remove filter only removes the message filter, the Source selection remains.

List

Column Meaning
Message Error message; up to two lines shown, hover to see full. If empty, shows (empty message). This column cannot be hidden.
Date Date and time the message was generated, including seconds.
Source Integration source producing the message.
Caller method Process where the message occurred.
Batch no Batch process number the message belongs to.
No Message record number.
  • The list is always sorted from newest to oldest; sorting by column headers is not supported.
  • Page size can be 10, 25, 50, or 100; default is 25.
  • You can hide or show columns from the Columns menu; your selection is saved in your browser.
  • Clicking a row or selecting Open detail from the three-dot menu opens the message drawer.

Message drawer

The drawer's title is in the format Log message #[number]. Below the title, the message's source and mapping status appear as badges. The open message number is written in the page URL; sharing the URL lets others see the same message open. Closing the drawer with Close keeps the list, filters, and page as is.

General tab

Field Description
Batch no Batch the message belongs to. If present, the All messages of this batch button is next to it.
Caller method Process where the message occurred.
Source Source producing the message.
Date Time the message was generated.
Message Full error message. You can copy it to clipboard with the copy icon at top right.

If the message is empty or consists only of spaces, a warning Message is empty or consists only of spaces: and visible spaces are shown.

Mapping tab

  • If the message has a mapping, the top shows the Text shown to the user (preview) box, below which are the mapping's No, Action (shown to user), Error message, Source, and Order fields with an Edit mapping button.
  • If no mapping exists, it says No mapping for this message and shows an Add mapping button. Mapping applies only if the error message and source exactly match, case-insensitive.

Actions

Viewing messages in the same batch

If multiple errors occurred in one batch process, to see them together:

  1. Open the General tab in the message drawer.
  2. Click the All messages of this batch button next to Batch no.
  3. The drawer closes, the list filters by that batch number and returns to the first page. Other applied filters (date range, source, etc.) remain; remove them if you want to see all messages of the batch.

Adding a mapping

Used to attach a user-visible explanation to an unmapped error message.

  1. Open the message and switch to the Mapping tab.
  2. Click Add mapping. The Add mapping window opens (the drawer hides while open and returns when closed); Error message and Source fields are prefilled with this message's values.
  3. Enter the explanation visible to the user in the Action (shown to user) field.
  4. Fill the Order field if needed.
  5. Click Continue. If there are errors in fields, warnings appear below them and the window does not proceed.
  6. In the Save this mapping? window, review the values and click Save. To cancel, click Cancel to return to the form.

Result: Mapping added notification appears, the window closes, and the list and drawer refresh. If the error message and source remain exactly the same, the badge in the drawer changes to Mapped.

Editing or deleting a mapping

  1. Open the message, go to the Mapping tab, and click Edit mapping. The window title changes to Edit mapping.
  2. Change fields and click Continue, then Save in the confirmation window. Mapping updated notification appears.
  3. To delete, click the Delete button at the bottom of the window. In the Delete the mapping? window, verify the No, Source, and Error message of the mapping to delete and confirm with Delete; Cancel returns to the form. Mapping deleted notification appears.

Notes:

  • Confirmation windows show the warning Changes take effect immediately in production: the explanation shown to users on orders with this error will change. Saving and deleting cannot be undone; deleted mappings must be re-added.
  • If the operation fails, Mapping could not be saved notification appears and you return to the form; your input is not lost. If mapping writing is disabled in the environment, Mapping writing is disabled in this environment; records are view-only. notification appears.
  • If you lack permission to add or edit mappings, the window shows Administrator rights and mapping write permission are required to add or edit mappings. warning and disables Continue and Delete buttons.

To list and manage all mappings in bulk, use the Message mapping screen.

Mapping form

Field Required Description / rule
Error message Yes Must be exactly the same as the log message. Saved as is; leading and trailing spaces are not trimmed. Messages consisting only of spaces are valid (used to map errors returning empty responses), but completely empty fields are not accepted.
Action (shown to user) Yes Explanation visible to the user. Leading and trailing spaces are trimmed on save. To include the raw error text inside the explanation, write …. When using this placeholder, a Preview box appears below showing how the text will appear to the user.
Source Yes Integration source producing the message; must be the same as in the log message. Maximum 100 characters; leading and trailing spaces are trimmed. Suggestions appear from existing mappings and this screen's Source options while typing.
Order No Integer. If multiple mappings exist for the same message, the one with the smallest order is applied. Can be left empty.

If the error message has leading or trailing spaces, a warning Error message has leading or trailing spaces; it will be saved as is. appears; if the message consists only of spaces, a warning Error message consists only of spaces. This can be intentionally used to map errors returning empty responses. appears. Validation warnings are Required field, Maximum 100 characters, and Must be an integer; they appear after pressing Continue.

Statuses

Status (text on screen) Meaning Next step
Mapped (green) A mapping is applied to the message; the user sees the explanation instead of the raw error. Verify the explanation is correct using the preview in the Mapping tab.
Not mapped (yellow) No mapping matches the message. If it is a frequently recurring error, add an explanation with Add mapping.

Common situations

  • "No log messages in this range" is shown. When no date is selected, only the last 10 days are searched. Expand the Date range or remove filters.
  • The source I am looking for is not in the Source list. Options only include sources appearing in the applied date range. Expand the range and press Filter.
  • I added a mapping but the message still shows "Not mapped". The error message and source must exactly match the log message; especially check leading and trailing spaces. When opening the message via Add mapping, fields are prefilled with correct values.
  • The list shows records for only one message text. The exact message filter is active; press Remove filter on the strip. Remove the Source selection if needed.
  • "Record not found" is shown in the drawer. The message you tried to open no longer exists. Close the drawer and refresh the list.
  • "Log service is not configured in this environment" is shown. This is not a fault but a missing setup. Contact your system administrator.

Related screens