Wappler Version : 6.2.1 Beta
Operating System : Windows 11
Server Model: Capacitor
Expected behavior
When clicking a “Next Page” button in my app, a variable should be set which immediately calls an App Flow that triggers a Capacitor SQLite Query to return the next page of records.
Actual behavior
The behavior does not work as expected. It works perfectly in Stable channel, but in Beta it requires setting a Debounce value.
If Beta will soon replace Stable, then maybe a default Debounce should be set automatically to ensure users do not run into similar issues.
Normally debounces should not be needed. Could you tell how you implemented it, where and how do you set the variable and when do you trigger the flow?
I have an on click event that sets/modifies a query param.
The currentPage variable is updated based on the query param, and it triggers the page flow when value is updated.
The Emails page flow runs various queries based on different parameters that may be passed in, but all have limit and offset values. The limit and offset values are variables.
You trigger the flow directly when the currentPage was updated while you have other variables that are dependent of it. A debounce indeed fixes it or you could add the updated event on the offset variable since it is the last variable to be updated. The updated event is triggered when the value of that component was updated, it doesn’t mean that all dependencies are also updated.
