Issue:

Our current system does not support the use of multiple yield statements within a single function, thereby limiting execution flow control. This becomes especially important when we wish to have execution spanning across multiple requests, which can't be achieved with our existing setup.

Expected Behavior:

A function should be able to include multiple yield statements, with each yield representing a pause point in execution until the next request triggers the continuation of execution from where it left off.

Steps to Reproduce:

Write a function that includes multiple yield statements.
Attempt to execute the function across multiple requests.
Observe that the function does not resume execution from the last yield upon a new request.
Suggested Solution:

Revise the system to support the use of multiple yield statements within a function, where each yield acts as a checkpoint. When a new request is made, the function should continue its execution from the last yield.

This will require modification to the function execution flow and potentially the addition of a mechanism to store the state of a function between requests.