Manual Guide: Incoming Logs¶
The Incoming Logs module serves as the main gateway for monitoring, recording, and managing all incoming requests received by the system through webhook models—supporting both synchronous and asynchronous processing.
1. Interface Overview¶
This page displays incoming request transaction logs in a DataTables grid, complete with status filters, search tools, and a dynamic slide-over panel integration for re-testing (Flow Tester).
- Action Toolbar (Top): Contains global action buttons for refreshing, exporting, and managing data views.
- DataTables Grid (Center): Displays the list of incoming transaction logs in real-time.
2. Request Status¶
Every request entering through the webhook—whether processed Synchronously or Asynchronously—is categorized into one of the following statuses within the table column:
| Status | Description |
|---|---|
| Pending | The request has just been received at the gateway and is queued for processing. |
| Processing | The system or worker is actively processing the request payload. |
| Timeout | The execution exceeded the predefined maximum time limit. |
| Error | A system issue or failure occurred while executing the request. |
| Skipped | The request was intentionally bypassed based on system logic rules or specific conditions. |
| Partial Success | Most data was processed successfully, but minor parts failed or require attention. |
| Completed | The request was fully completed without any issues. |
3. Key Feature: Reply & Flow Tester Integration¶
One of the standout features in this module is the ability to perform a Reply (Re-simulation) on a previously logged request.
How to Use the Reply Feature:¶
- Locate the specific request log entry you want to re-test in the Incoming Logs table.
- Click edit or double click the row. The slide-over panel on the right side of the screen will automatically open in Update mode.
- Click the button.
- The slide-over panel on the right side of the screen will automatically open in Flow Tester mode, where the following data is automatically populated based on the selected log:
- Endpoint URL target
- JSON Body (Original payload data from the log).
- Request Headers (Original authentication metadata/header parameters).
- Review the pre-filled data, then simply click the Send button to re-dispatch the request to the system.
4. Standard Table Operations¶
For complete guidelines on how to use standard table utility features (such as ColVis, copying data, Export/Import, Refresh, Bulk Delete, etc.), please refer to the Standard Tables Guide.