You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to determine north star metrics like solve latency, we need historical timestamps as a request goes through status updates. We also need to see which request was most recently switched to any given status.
Proposed Solution
Add update history to the requests and include a mapping binding each status value to the most recent request to apply it.
The text was updated successfully, but these errors were encountered:
Added `getLatestRequestByStatus(status)`, which retrieves the most
recent request to be set to a particular status. I also replaced the
`deployedAt` Arbitrum branch handling with something much more robust.
I attempted to add `getRequestUpdateHistory(id)`, which would return the
timestamp history for all status updates a request has undergone.
Despite this not altering the request and fulfillment flows, it broke
the e2e tests, so this has been excluded for now.
issue: #2679
Problem to Solve
In order to determine north star metrics like solve latency, we need historical timestamps as a request goes through status updates. We also need to see which request was most recently switched to any given status.
Proposed Solution
Add update history to the requests and include a mapping binding each status value to the most recent request to apply it.
The text was updated successfully, but these errors were encountered: