According to http://docs.aws.amazon.com/amazonswf/latest/developerguide/swf-dg-limits.html, the max of any SWF request is 1 MB, we handle most limits properly in simple-swf by using claim checks. However, this limit can hit if you try and make a ton of decisions in a single response.
This will probably be a tough one to deal with... a naive and probably would work as currently implemented solution would just be to drop the decisions and assume that another decision will happen and reschedule (since the decider is a pure function, this should work). However, it would probably be a hindrance for future deciders that may not be pure functions
According to http://docs.aws.amazon.com/amazonswf/latest/developerguide/swf-dg-limits.html, the max of any SWF request is 1 MB, we handle most limits properly in simple-swf by using claim checks. However, this limit can hit if you try and make a ton of decisions in a single response.
This will probably be a tough one to deal with... a naive and probably would work as currently implemented solution would just be to drop the decisions and assume that another decision will happen and reschedule (since the decider is a pure function, this should work). However, it would probably be a hindrance for future deciders that may not be pure functions