4
Flow functions after an Alert node do not get triggered in web runtime
complete
G
Greg Florkow
The scenario works fine if the Alert is directly after record update, but preceding it with Alert will not cause to navigate back.
Log In
Activity Feed
Sort by
H
Harri Sarsa
complete
This is now fixed with the latest release, see https://docs.appgyver.com/changelog#release-146-2020-12-11
G
Greg Florkow
I have just spent 30 min trying to understand why my workflow doesn't work. Than I realized that there used to be this but related to Alert execution on the web.... The bugs are really the biggest issue with appgyver.
H
Harri Sarsa
in progress
Fixed with v2 runtime!
G
Greg Florkow
Harri Sarsa seems this is still unresolved? This should be an easy fix?
H
Harri Sarsa
Merged in a post:
Flow function Alert - no output
G
Greg Florkow
This function has not output, which is sort of logical, because there is no other option than press OK. However this means that anything linked to the connector on the right hand side of the "Alert" will not be triggered.
This means that either the function should have some output (like "OK") or it should have not connector on the right hand side. Otherwise you can create a "dead alley."
H
Harri Sarsa
Actually affects all logic on web that happens after an alert node.
H
Harri Sarsa
planned
H
Harri Sarsa
Things after Alert SHOULD get triggered (but only after the user presses OK); the presence of output arguments is not a factor – but I believe there is a bug where web alerts don't trigger logic afterwards. Is this happening to you on web? That anyway definitely needs to be fixed.
G
Greg Florkow
Harri Sarsa: confirmed - it does work fine on android preview. The web app version is having issues.
H
Harri Sarsa
Valid catch, should fix this!