Forum
How to ensure process-end when making websites with Appway




In a website - such as the Appway blog - users are not expected to follow a fixed track; but rather browse around randomly. As a result, they may create 100s of process instances - some still in use; others abandoned by simply closing the browser.
- How does Appway determine and cleanup the inactive process instances?
- I imagine this being linked to user session expiry - in case the website has user authentication. What - if any - config param will terminate process instances of a logged out user?
- How will this work in case the website is public - with no user authentication?



