Error reference

What the messages in the PROBLEMS panel mean, and which ones you can do something about.

First: is it yours or ours?

PIES Studio sorts build problems into two kinds, and the difference decides what you should do.

Kind	What it means	What to do
Application	Something in your application is incomplete or contradictory — a step with nothing configured, a widget bound to nothing.	Fix it in the editor, or ask PIES AI to. The messages below are all of this kind.
Platform	The generated code itself is wrong. Your application is fine; our code generator is not.	Not fixable in the editor. Report it — nothing you change in your application will clear it.

Application problems name one of your things: a screen, an event, a function, a table. Platform problems read like compiler output about generated code you never wrote. If a problem quotes source that is not yours and repeats after the automatic repair cycle gives up, it is ours — send it to us rather than working around it.

Steps and logic

"has an orphan step … with no incoming link" A step is sitting in the flow with nothing leading to it, so it can never run. Open the event or function and link it from the step that should come before.

"has a dead-end step … with no outgoing link" The mirror of the same problem: a step nothing follows. Every step except the end must lead somewhere.

"must have exactly one start step" / "must have at least one end step" The flow does not begin or does not finish. Add the missing step.

"link references unknown from-step / to-step" A link points at a step that is no longer there — usually after deleting a step without repairing the flow around it. Delete the dangling link and reconnect.

"has duplicate step id" Two steps share an identity. This one is not repairable by hand; rebuild the event, or ask PIES AI to.

"step … has no configuration" The step exists but nothing was filled in. The message names what it needs.

"the If step … has NO condition" An If with nothing to test cannot compile. Give it a condition or remove it.

"blocks are never closed" Something opened — an If, a loop — and never ended. The message says how many more end steps are needed.

Data

"Table Missing Data Source" A table exists in the data model with no source behind it. Bind it, or delete it if it was created by mistake.

"step … has no dataSource" A record step that does not say which table to read or write. The message lists the tables it can be bound to.

"Set Record Value step … assigns no column values" The step saves nothing. Either give it columns to set, or remove it.

"Set Record Value step … is missing variableName and/or type" The step does not say what it is building. Reopen it and complete the first constraint.

Screens and widgets

"step … is missing the target screen" A navigation step with no destination. Choose the screen it should open.

"has an invalid navigation step" Navigation was given something that is not a screen. Pick a real one.

"the Custom Widget step … has no code block" A custom widget with no code in it. Add the code block, or delete the widget.

A screen that builds cleanly but shows nothing

Not an error message — the most common report that is not one. In order of likelihood:

The widget is bound to nothing. Select it and check its data source.
Nothing delivers the data. A widget that expects rows needs the screen's onload event to fetch them and hand them over. No onload event, no data.
The function returns nothing. It reads records but never returns them.
The widget is outside the drawable area. It rendered — past the right edge. Check its position.

When the build will not go clean

PIES Studio retries automatically, feeding each failure back for repair. If it stops before the build is clean it tells you why:

Stuck on your application — the remaining problems need a decision only you can make. The list is in PROBLEMS.
Stuck on the platform — the remaining problems are in generated code. Report them; there is nothing to change in your application.
Mixed — some of each. Fix yours, report ours.

That distinction is the point of the message. It exists so you do not spend an afternoon rewriting a screen that was never the problem.