flow.* and processor.* events the engine recorded while it ran, newest or oldest
first, with an optional filter and cursor pagination. The log is described on
Execution Events. The execution’s lifecycle events, such as
execution.started and execution.ended, are on the session stream:
List Session Events.
POST /revisions/:id/data/query (Command: list_execution_events)
Request Body
Response
Pagination. Pass the response
cursor back as the request cursor to fetch the next page; stop when cursor is
null. The cursor is opaque, so send it back verbatim. It resumes after the last row evaluated, and it keeps the
after or before that bounded the first page.
Evaluation budget. The filter runs on the server. A request keeps reading until it has limit matches, the range is
exhausted, or it has evaluated 10,000 rows. Only that budget can end a page short while cursor is still live, so keep
reading until cursor is null.

