How is your experience with the OutSystems Community?
22
Views
6
Comments
ODC possible bug on action flow

Good evening,
I was testing the ODC Studio AI Mentor functionality, and it generated a flow that, to me, makes no sense, but the ODC is not detecting as an error.  When I tried to publish it, it gave me an "OS-BEW-50000".


Just to be clear, this is a ODC bug, right? This kind of flow makes no sense to me, and that the ODC Studio doesn't mark it as an error it's also kind of confusing

2026-06-03 12-13-54
Jasper Oudenaarden

Hmm....that looks interesting!

Normally when you have a separate flow without a start/end node within Service Studio you receive an error straight away. Not even mentioning the infinit loop!

Mentor must have special permissions/rights to fool the system then?! 😂

2026-06-05 12-38-17
Eduardo Jauch

Hello @Fabian Luz ,

Any element, to be considered correct must have all it's required connections connected to a Node.
We all now the rule: The logic flow starts at the Start node and finishes on one of the possible End nodes.

If you have an element connected to another but neither are connected to the main flow, you will see the two error messages (one on each node) saying you are missing one outgoing connector to the flow and one incoming connector from the flow.

So, naturally, we would not make something like that.

But now, if make the second connection creating a "loop" between the elements (like you have on your code), the error disappears, because it is following the rule. A server action needs an entering connection and a leaving connection. And it's correct.

Of course, when you try to compile, the compiler does not know "where" to put that code, because it should be in the "main flow", but it's not. Hence the error.

In this case, AI Mentor, for some reason, made a small mistake, leaving the assign node and the entity action node outside the logic flow, but fixed it by connecting the nodes to each other. No errors! :D

I would say it's an oversight from the team that made the code to validate the logic flow.
Instead of validating if the node is somehow connected to the flow, it's just checking if all its connections are connected.

Of course, AI Mentor should not create this type of code.

I recommend you to send feedback and include your application in the feedback to facilitate the team to analyze and make a fix for this.

Cheers!

2020-09-15 13-07-23
Kilian Hekhuis
 
MVP

Hi Fabian,

If this is generated by AI Mentor, that seems a bug. However, the possibility to create such a flow has always been possible manually, strangely enough, not just in ODC but in "O11" (pre version 11).

2023-03-23 09-36-18
Fabian Luz

Yeah, it looks like I can do it manually too (that also makes little sense), but the more i'm trying to test the application and generate things with AI Mentor, the less sense it makes
For example...It's generating "Create" actions of my entities...with the source completely blocked, in a way that i can do manually:


Just to be clear, that entity has mandatory fields, and I would not be able to do that:


And If I ask Mentor about it, it finds no error about it.
Does this makes sense? Has mentor like a background data that is passing to the sources in a way the normal user is not able to read or something like that?


Just to be clear, I can do this by hand, I'm just trying to see the current capabilities of Mentor and I'm not really understanding half of the things is doing

RoadmapAITest.oml
2026-06-05 12-38-17
Eduardo Jauch

Ok.

I understand the question now...
This is REALLY weird.

Mentor should just create "normal code".
Again, if it's creating something "weird", you should submit a feedback, or open a support ticket.

Cheers.

2023-03-23 09-36-18
Fabian Luz

I've just sent a "Report Issue" from the ODC Studio, thank you to everyone for the help. Maybe I have bad luck or something, but my experience with AI Mentor is being...not amazing. Thank you!

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.