Closed neelvirdy closed 1 year ago
Note for potential future improvement: Replace readinessReason in the backend with a struct that includes a readinessReasonCode and relevant metadata for the readiness state, so that the frontend can handle the actual language and formatting of the message.
Corresponding estuary PR, which includes the readiness state logic: https://github.com/application-research/estuary/pull/479
Problem
It can be unclear why staging zones are not turning into deals and how to get them unstuck. The logic used for staging zone readiness is buried in code and that is the only place it's discoverable. This can be especially frustrating for new users and deter them from following through on using estuary.
Solution
Display readiness state and reasoning on the Staging page so the end user can understand how we're evaluating their staging zone.
Example
Note
Tested there is no effect if the estuary version does not provide the readiness info: