The Debugger is a tool for testing module execution and external API calls without going through the production application. Use it to send test requests, inspect the full execution flow step by step, and trace exactly how data moves through a module's server-side logic.
Access the Debugger by selecting Debugger from the Definition drop-down in the Module Builder header. Access the Server Side Execution Testing page by clicking Open SSE Debugger in the Service Logs panel.
Internal vs. External
The Debugger operates in two modes, toggled at the top of the page:
- Internal: Tests Unqork module execution. Select a module API endpoint, configure the request body and options, and run the module against test data.
- External: Tests external API calls against services configured in Services Administration. Select a service, set the HTTP method and URL, configure the request, and execute directly.
Internal Mode
Request Configuration
Select the module API endpoint to test from the Search APIs drop-down. The HTTP method and URL populate automatically.
Expand Execute Options to configure additional request settings:
| Setting | Description |
|---|---|
| ID | An optional submission ID to use as the basis for the execution. Leave empty to begin with a new submission. |
| Save | When checked, this setting persists the submitted data to the submission after execution. |
| Validate | When checked, this setting runs validation against the module schema during execution. |
| Load Submission Data First | When checked, this setting populates the request with data from the existing submission before applying test data. |
Configure the request using the tabs below Execute Options:
| Tab | Description |
|---|---|
| Docs | Inline API documentation for the endpoint selected in the drop-down above. Updates automatically when you change the selected endpoint. |
| Params | query parameters to include with the request. |
| Headers | HTTP headers to include with the request. |
| Body | The request body. Toggle between key-Value (structured editor with nested group support) and Raw JSON (direct JSON input). |
Click Execute to run the request.
External Mode
Select a configured service from the Search services drop-down. Set the HTTP method and enter the target URL. Configure the request using the Docs, Params, Headers, and Body tabs, then click Execute.
Execution Results
After the module executes, results display in the bottom panel. The header shows the HTTP status code, total response time, a View Module Service Logs link that opens the module's service logs in a new tab, and a Clear button to reset the results.
Select a tab to inspect different aspects of the execution:
| Tab | Description |
|---|---|
| Response | The full JSON response body returned by the execution. Includes a Copy button to copy the response to the clipboard. |
| Event Log | A chronological list of every event that occurred during the execution, organized by step. Each event shows its type (START, SET, and so on), the affected field, timestamp, and time offset. |
| Data Changes | All fields that changed value during the execution, grouped by step. Expand any entry to see the before and after values. |
| Timeline | A visual chart showing the duration and sequence of events across the execution, color-coded by event type: Execute, Async, Data, Trigger, and Watcher. |
| Execution Chain | The trigger relationships between components during the execution. Displays when one component triggered another. |
The Group by step control on Event Log, Data Changes, and Timeline organizes results by execution step. Collapse all collapses all expanded entries.
Changelog
| Date | Change |
|---|---|
| 2026-05-29 | Full rewrite for new IDE Debugger — Internal/External modes, updated results tabs. |