Hi there, is there any plan to support

after_cursor

and

before_cursor

in

RunsFilter

like with

EventRecordsFilter

?

Hi Son. What’s the use case you’re looking for? With events, there’s an implicit ordering (time), but with runs, it’s a little less clear, since you could order by creation time, completion time, update time, etc.

Hi Son, just following up here-- are you still wondering about this question?

Hi, I think the

RunsFilter

is weird because it has

updated_after

but not

updated_before

and

created_before

but not

created_after

, which is not good because some use-case I might use that. Also, the

cursor

parameter in

DagsterInstance.get_run_records

is weird and seems like it doesn’t behave like

after_cursor

and

before_cursor

in

EventRecordsFilter

.