better error loging

**yuri** · 2026-03-19T13:45:13+00:00

Most errors can be tracked down by enabling tracing in the log. It's how it's supposed to work.

Some log messages are not traced, if there are some important, each one should be fixed separately. There's no single engine that we can fix so all log messages are traced.

> Just what is the point of giving errors i can't track down?

There's no need to write this in a feature request other than to add more toxic tone to it.

**jamie** · 2026-03-19T15:08:28+00:00

It's meant to share my sense of frustration at seeing a massive amount of errors in my setup, but because of obscurity, doing anything about this is very difficult

Well, maybe it's time to have all errors feed through a single log function so they can be better handled and traced. Many of them list the offending workflow ID, and that's all I need, but without any source of reference, I am probably going to have to write my own script just to handle the shortcomings of the output

**yuri** · 2026-03-19T15:19:02+00:00

The all go through the standard PSR logger. In case of exceptions, they can be traced. In case of notices (just message), they can't be easily traced. We can add some context, and sometime we do add, but often it's very hard to know the exact context at it occurs very deep. We try not to use notices and prefer errors now, it's usually a legacy code that can't be changed to prevent compatibility breaks.

**jamie** · 2026-03-20T08:28:48+00:00

if you could just always display the workflow id that would be amazing

**yuri** · 2026-03-20T08:35:01+00:00

Yes, but understand the the formula function is not aware of the workflows feature neither any other potential future feature it will be called from. How it's suppose to work: when an error occurred in a formula function, it is bubbled up until it's caught by something above. I believe we do it for workflow and display the ID. Not sure if it's always the case, need to check.

For notices it's impossible to display the workflow ID.

For "Workflow: Could not get related entity by path", it's possible and we should fix it (unfortunately the fix is not trivial in this particular case). But it's really the case that is not a real error and could be even lowered to the INFO level.

better error loging

better error loging

Comment

Comment

Comment

Comment

Comment