Process Logs

Review background activity, investigate failures, and understand processing outcomes.

This guide is for tenant administrators and operational users who monitor queued and worker-driven activity in WennSoft Cloud. Process Logs helps you confirm whether work completed, identify skipped records or warnings, and collect useful details when a process fails.

Open Process Logs

From Settings, expand Monitoring and select Process Logs. The page opens with the newest started activity first and shows up to 50 records on the current page.

You may also arrive here by selecting Open Process Logs on a persistent background-failure notification. That action appears only when your role can access the page.

Filter the Activity List

Use filters to narrow the server results before reviewing a run.

Complete the following fields:

• Search (Optional) Enter all or part of a process name, request path, or correlation id. Leave this field blank to include all matching processes.

• Status (Optional) Choose All, Pending, Processing, Succeeded, or Failed. All is the default and does not limit the list by status.

Select Apply to rerun the search. Select Clear to reset both filters and return to page 1. The summary above the grid shows how many records are loaded and the total number of matches.

Read the List Results

Use the grid to identify the run you need. Select a sortable column heading to change the order; changing the sort returns the list to page 1. Use the paging controls when more results are available.

• Started On: The local date and time when processing began. Select this link to open the full record.

• Process: The name of the background operation.

• Status: Pending has not started, Processing is underway, Succeeded completed, and Failed ended with an error.

• Skipped: The number of records intentionally left unchanged when the process publishes a skipped count. A dash means no positive skipped count is available.

• Method and Request Path: The action and product location associated with the request.

• Correlation Id: A trace value that links the request to its processing record. Use it to find a specific run or share it with support.

• Duration (ms): Elapsed processing time in milliseconds. A dash appears when no duration is available.

Open a Process Log

Select the Started On value for the run. The Process Log Detail drawer loads that record without replacing the list.

• Process and Status: Identify the operation and its current or final state.

• Started On, Completed On, and Duration (ms): Show when the run began, when it ended, and how long it took. A dash indicates that a value is not available yet.

• Correlation Id: Provides the trace value for this specific run.

• Request Path and Request Method: Show the customer action that queued or recorded the operation.

• Process Model: Shows the process context when the operation provides it.

• Request Payload: Shows the submitted processing values when the operation provides them.

• Outcome: Shows the recorded result, summary counters, step entries, or formatted raw detail.

• Errors: Lists customer-visible error messages for a failed run when errors are available.

Interpret the Outcome

Outcome presentation varies by process type. Start with the summary shown in the drawer, then expand Raw Outcome when you need the complete recorded detail.

• Step-based outcomes: Each entry shows a Step number, step name, Timestamp, and Data. Read entries in order to follow the run's progress.

• GL Account outcomes: Review Processed, Inserted, Updated, and Failed totals. Skip Reasons groups the causes of skipped accounts, and Skipped Accounts lists the account number, reason, and external id. A message indicates when only the first portion of the skipped-account list is displayed.

• Purchase Order outcomes: Review separate summaries for Purchase Order Headers and Purchase Order Lines. Header totals include Processed, Inserted, Updated, and No Change; line totals include Processed, Inserted, Updated, and Failed.

• Raw outcomes: Formatted detail appears when no specialized summary exists. The Raw Outcome label includes a warning count when warnings are present.

• Important: Migration and summary counters apply only to the selected process run. Do not treat them as lifetime totals.

Investigate an Incomplete or Failed Run

Use the following sequence to collect the clearest troubleshooting evidence:

• Confirm the Status and note whether the Skipped column contains a count.

• Open the detail drawer and review Outcome, warning counts, skip reasons, and Errors.

• Copy the Correlation Id and note the Process and Started On time so the run can be identified precisely.

• Correct the originating data or configuration only when the outcome clearly identifies the needed change; otherwise provide the collected details to your administrator or support contact.

Refresh and Finish Your Review

Select Refresh to reload the current query without leaving the page. Close the detail drawer when you are finished; your filtered list remains available for continued review.

Process logs are retained for a configured period and older entries are removed automatically. Complete investigations promptly, especially when you need to preserve a correlation id or error detail for support.