🐞 Bug Report – Issue with Return a Value in component workflows

[Artur.AppDaHorta]

I’ve found an inconsistent behavior when using the Return a Value action in WeWeb:

• When using Return a Value in global workflows, it works as expected.

• But when the workflow is created inside a component, the return only works if the workflow is executed within the same component.

• If the workflow is executed from outside (even with Allow execution from outside enabled), the Return a Value always comes back empty.

In screenshot 1, you can see the workflow created inside a component, with Return a Value properly configured and Allow execution from outside enabled.

In screenshot 2, you can see the same workflow being called from outside the component. In the logs, the return is processed correctly, but the action’s Return is empty.

Summary

• Inside the component: return works fine.

• Called from outside the component: return is empty.

It seems to be a bug in how WeWeb handles return values when the workflow execution comes from outside the component.

[Artur.AppDaHorta]

Solution found

I managed to solve this issue by using Custom JavaScript instead of relying only on the standard return action.
The key point is that, when calling a component workflow from outside, you need to use await to properly capture the value.

Example:

return await context.workflow[‘—ID Workflow—’].result;

With await, the return value shows up correctly and works as expected.

[Agustin_Carozo]

Hi Artur, welcome back

Thank you for brining our attention to this issue.

Have you opened a support chat so we can take a better look at your project?

In the meantime I’ll talk with our tech team to understand if this is a normal behavior or not.