My current and previous version of ODC Studio is playing some tricks recently.
When debugging an application, the values for elements in "In Use", "Locals", "Widgets" are all showing "(Unavailable)".
I am using ODC Studio 1.6.14/Build 9257
App was built using AI Mentor and I am making changes on the app currently. (Will test other apps to narrow down the issue)
Hello everyone, I can confirm the issue is now fixed! Thank you for your patiente.
Thank you, @Marcelo Penas .
Hello.
It is a known OutSystems feature that the code is optimized. Unless the values are used, they are not calculated or shown.
https://success.outsystems.com/support/troubleshooting/incident_models/incident_models_outsystems_developer_cloud/debugger_output_values_may_have_empty_or_false_values_when_executing_actions/
Are you actually using any of the variables on the screen?
Thanks for the quick response, @Nuno Reis . I looked at the link. No, I am not using any of the values on the screen, they are to be processed and put into the DB with some adjustments to the values and logic/
I have another server action in the flow and I can see the values there. However, since I am checking values and making adjustments to the variables and to the logic accordingly, I find it a little strange, especially that coming from traditional way of coding.
I am presuming there is no setting to turn this on or off?
You have this in traditional coding. It is called lazy evaluation and Haskell was my language before OutSystems, so that makes me a very lazy programmer in the best sense of the word :)
No, it is not possible to turn off.
If the values are send, they should be available in the debug. Try restarting Studio.
To add in, I think we can do some tricks for debugging:
I seem to be having the same issue with my ODC personal edition. All values are (Unavailable) when debugging.
ODC Studio
Version 1.6.15 / Build 9258
Again, is the variable used on the screen?
The way I see it, that assign is useless so the action was probably optimized to remove it.
Yes. It is shown on screen via the Expression.
I can confirm that debugger is not showing values (testing in the MVP organisation)
I have asked Outsystems if this is a known problem.
I'm having the same issue with an app created by Mentor AI.
Hello everyone! Thank you all for reporting, this is indeed a known issue we are working to fix asap. I'll keep you posted here.
Hello Marcelo'
Have you heard anything about this item. I am not able to debug my applications and even though I have a case open with Outsystems that has been acknowledged, I have not received any additional information. I wonder if you have anything more recent?
thank you...
I’m also experiencing this issue. During debugging, variables frequently appear as “unavailable”, which makes it very hard to troubleshoot properly.
As a workaround, I’ve been using JavaScript with console.log() to inspect values, but this significantly slows down development and is far from the ideal or expected debugging experience.
Glad to hear it’s already being investigated — this would be a very important fix for day-to-day development.
@Pedro Antunes,
this bug is very recent, and shows ALL variables as unavailable ALL the time.
The feature that SOME variables SOMETIMES are unavailable will still remain, this is a consequence of the code being optimized, and only data that is used is available.
Thank you @Dorine Boudry for your reply.
I understand that the platform applies some optimizations during debugging. However, I’m noticing that actions which previously returned values now do not, even when the same variables are used across screens. These variables should be recognized as in use and not affected by this optimization process.
Hello everyone,
I'm also experiencing this. All variables and elements in the debugger appear as unavailable.
I will follow this post.
I have an open case right now. It has been confirmed by OutSystems that this is a problem. No resolution yet.
I am currently using
Version 1.6.15 / Build 9328
And since friday the 16th of jan 2026 it works. I now see the values of the varibles in my Personal edition. Thank you for fixing this!
It is fixed. Important-I was asked to 'publish' in order for the fix to work.