You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Workflows does not have explicit input and output size limits (for Fission funtions). However, implicitly there are (for example: NATS has a 10 MB message limit), which causes unanticipated behavior---as the user is not aware of these limits.
To fix this, Workflows should have explicit message limits, and return an error immediately when the inputs or outputs exceed the limit.
cc @thenamly
The text was updated successfully, but these errors were encountered:
Currently Workflows does not have explicit input and output size limits (for Fission funtions). However, implicitly there are (for example: NATS has a 10 MB message limit), which causes unanticipated behavior---as the user is not aware of these limits.
To fix this, Workflows should have explicit message limits, and return an error immediately when the inputs or outputs exceed the limit.
cc @thenamly
The text was updated successfully, but these errors were encountered: