Debugging Behaviours feels painful

ScriptRunner
,
1

Does anyone else run into a very painful debugging experience in Behaviours?

First of all, needing to do a refresh any time you want to see new logs come in. But worse, the error handling seems such that sometimes the fired Behaviour isn’t logged at all.

Some examples of this occurring:

  • if no fields are affected, whether dynamically or because you’re not changing their state in your script,
  • if you try to log a non-string value to a template string (including numbers). The only way to figure this out is to delete the line, or to call toString() on whichever value you’re trying to pass.
  • if for whatever reason an API call fails. I tried try/catching it, logging status code, but no. It just doesn’t include the entire Behaviour call in the logs.

Am I missing something? As it stands it feels unworkable to me…

2

Been in touch with their support. If anyone else is having this issue: it doesn’t seem to be documented but logger messages are actually printed in the browser console log.

For some reason they show in the browser console log but not on the logger page. So if you have the same issue, just use the browser console to debug.