Tooling. IDEs and special languages to generate the files for the state transitions, and the body of the lambdas themselves. (reading this kind of made me want to go write a little haskell dsl)

If they're a little undisciplined, they'll probably add stuff to implement counting and comparison directly, to put a hard limit on loops.

I'd also guess an addition of a couple special tasks, perhaps append to log in s3 bucket and continue, that perhaps come with a discount.

There are about 3 million old flowchart tools out there, any feature you see tacked on is a candidate.

Tangentially, other organizations will be inspired by this, and implement their own language in json, but this time they'll do it "the right way" then you'll get a working group to try to reconcile all the competing standards.

Or maybe not. kind of what happened with XML though.

edit

ah, here you go. https://www.w3.org/TR/scxml/ that stuff.

You are in a twisty little maze of [standards], all alike.