1. Check the log for the call itself.
For outbound calls Nextworld makes to an external system, use the Endpoint Log Inquiry application. Logs show the resolved URL, headers, request and response body, and response code. Endpoint logs are purged after 5 days.
For inbound events an external system sends into Nextworld through the webhook feature, use the Webhook Log Inquiry application. Only unsuccessful events show by default. Enable logging for successful events in the Webhook Setup record for the webhook definition.
For a direct inbound call to a logic block or table's own REST endpoint, not through the webhook feature, use the System Log Inquiry application filtered to the Inbound API Request activity type. Every logic block and table exposes its own endpoint, so this is a separate path from both outbound calls and webhooks.
2. For webhooks, also check event delivery.
A webhook that logs successfully still has to be mapped into an event definition and routed to its target. Use the Event Target Delivery Status Inquiry application to confirm the resulting event actually delivered. Use the Event Status Inquiry application to review the status of the emitted event itself, including errors, and to resubmit a failure once the issue is resolved.
3. If the logs don't explain the result, verify the configuration.
Confirm the Webhook Definition, Webhook Setup, Event Definition, and Event Rule Definition records are set up as expected. The event rule is what maps the payload to its logic block target, so a misconfigured rule can prevent delivery even when the webhook itself logged successfully.
4. Confirm the record changed.
Use the Audit Log application to see whether the expected insert, update, or delete actually happened. Audit Log tracks changes to any record for any reason, so it's the general way to confirm the result even though it isn't integration specific.
5. Use System Log Inquiry when you need more detail.
The System Log Inquiry application captures a broader range of platform activity, including logic block execution, database errors, and REST API requests, filterable by date range, level, and activity type. Info, Warning, and Error level logging is always active, retained for 7 days.
Debug level is off by default, enable it in the System Log Configuration application for up to 8 hours per activity type when you need execution-level detail. Request and response bodies are never recorded here, for size and data security reasons.
Cross referencing across applications
Correlation ID always exists for any activity that starts at an entry point like an API call. Either the caller passes one in, or Nextworld generates one at that entry point, and every downstream activity triggered from there, synchronous or asynchronous, carries the same ID. Add the Correlation ID field to the list view in Endpoint Log Inquiry, Webhook Log Inquiry, Event Target Delivery Status Inquiry, and System Log Inquiry to visually match the records for one event across every application it touched.