Server action outputs not always updating on save

Wappler Version : 4.0.0 Beta 13
Operating System : Mac
Server Model: Node JS
Database Type: My Sql
Hosting Type: Docker

Expected behavior
When editing a existing server action step like a query from for example paged to multiple on save these changes should be seen in the data binds on the actual pages.

Actual behavior
After you edit the query from paged to multiple then going into a page to bind them the new outputs aren’t displayed and the old ones remain until you turn off the output on the query and back on again

How to reproduce
Edit a existing server action changing something like a query from multiple to paged etc then save the action file and check the available binds on your page (not sure if this is just something in my setup or if it happens all the time)

Can you please be more specific, what exactly does not update on your page and how do you expect it to update?


Server action multiple query

On the actual front end page binds

As you can see before editing I have a multiple query which shows as 3 lines in the app binding


Server action multiple query edited to paged

On the actual front end page binds again

After I change this to a paged query and save the action I then don’t see the updated binds for the paged query still see the ones for multiple, I have also tried refreshing in the app binds menu it doesn’t update until in the server action I disable then enable output on the query save and it updates in app binds

What do you mean? What dialog is that? How do you open it? Did you save you server action after making these changes?

Yeah was saved after each edit and by that I meant this menu

the one used to bind data onto the pages etc

So you chage a database query from paged to multiple, save the server action, open your page and try to bind some data on the page?

Yeah that’s it

So is it a content page?
Where is the server action included - on the content page or on the layout page?

Yeah its on a content page and the action is also on the content page

Was doing some tests to try narrow down the issue seems to be happening in a repeat I tried a different test with no repeat and was seeming okay havent tried conditions etc