Following up, we need a similar array input for listTasks too, so we could use one cursor to control all the results. For example,
listTasks([smartWallet1, smartWallet2, smartWallet3], cursor

Cursor related: from the below screenshot, we can see that the filter and sorting of column needs to be done by the server side. I don’t think we need them, especially the sorting, now, but here are the feature required.

Filter(P2):

1. by Status: active, completed, etc.
2. by completedAt timestamp: using epoch for within last month, or last 3 months

Sort(P3):

1. By completedAt timestamps: desc by default, but asc could be useful.
2. By Status: display Active first, then others
3. Type: by the type of trigger

@chrisli30 Agree with listTask. Thinking of same thing. I actually plan for all of this to filter by status and type before and I agree with that.

Filter(P2):

by Status: active, completed, etc.
by completedAt timestamp: using epoch for within last month, or last 3 months: 

For sorting, right now we sort by started time when a workflow is triggered in asc filter. It has similar effect to completedAt in term of sorting.

Is the hard requirement to be completedAt or startedAt is fine? They has similar effect in term of sorting.

For sorting by status and type, i feel like this should just be filtered ? filter by active/type first, then sort by startedAt normally.

Is the hard requirement to be completedAt or startedAt is fine? They has similar effect in term of sorting.

Okay, let’s use startedAt in a desc order.

For sorting by status and type, i feel like this should just be filtered ? filter by active/type first, then sort by startedAt normally.

Right, status and type should be filters.

startedAt needs to be both a filter, and a sorter. The filter will help us to retrieve executions within a week.

listTasks([smartWallet1, smartWallet2, smartWallet3], cursor
getExecutions(smartWallets: [], cursor: string, options)

This is done now. We will pass an array to list tasks and get execution.