- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2023 07:26 AM
I can't get Script Debugger to trigger. Here is what I have done:
1. Write gs.info("TEST"); on the first line. Set a breakpoint to this line.
2. Create an order that will trigger the script (it's a script for an Approval Workflow step).
3. Check in the system logs, "TEST" is there.
4. Open the Script Debugger. The script is there, the breakpoint is there. Status: WAITING_FOR_FIRST_BREAKPOINT
I have done many variations on the same thing, but alas! What could be the problem?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2023 07:41 AM
Hi
you only can debug script code which is running in your session in the "foreground".
However workflows are executed in the background decoupled from the user session therefore it will not work.
Maik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2023 07:41 AM
Hi
you only can debug script code which is running in your session in the "foreground".
However workflows are executed in the background decoupled from the user session therefore it will not work.
Maik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2023 11:28 PM
Thanks, I guess that answers my question.
Could you please enumerate which scripts run in the background? I'm guessing: background scripts (Scripts - background), workflow scripts, scheduled scripts... is there anything else?
Much appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2023 12:21 AM
basically you can narrow down it to everything which is triggered from the jobs defined at table sys_trigger. This includes everything you mentioned and more.
Maik