How to debug logic blocks in Nextworld that get kicked off due to an inbound endpoint request made from a REST client like Postman

Nextworld Platform How Tos
1

This has existed for sometime, but is something the Partner Dev team recently learned about. Official documentation on how to do this is coming soon. In the mean time, here’s a basic outline:

  • Configure the payload with an additional parameter

    • For table endpoints that have triggers or action blocks to debug, add "nwDebugMode": true to the body of the payload

    image
    image1405×436 35.4 KB

    • For traditional table-based logic block :execute endpoints, add “debug": true to the body of the payload inside of the ”logicBlocks” array, for example

      {
      …
      "logicBlocks": [
      {
      "logicBlockName": "xxx",
      "debug": true
      }
      ],
      …
      }

    • IMPORTANT: Multiple input/output :executeWithSignatures logic blocks do not currently support direct debugging

  • Send your Postman request.

  • Depending on the type of tenant, you may or may not get a debug notification. If you don’t get a notification, follow the steps below to open the debug session.

    • In Nextworld, open any logic block in builder view.
      • In Options, set Debug to true
      • Refresh the session which should find the debugging session that was created.

image
image571×318 19.4 KB

image
image1759×277 29.5 KB

9 Likes
4

Pressing Refresh in the debugger should cause the session to appear. Are you saying that’s not happening?

Is it possible you are calling the endpoint against a different Environment than the one you have the debugger open in?

Is your authorization token for the same user you are logging in with?

5

I think we need to add “debug": true in the below section:

image
image540×415 13.8 KB

1 Like
6

Thankyou @nishit.jain! I have updated the original post to correct it and hopefully make it more clear.

1 Like