One of the most irritating things a tool can do is tell you that you have made a mistake when it has not finished checking.
I check whether the interface has finished loading before believing its warning. A saved selection can be valid even when the supporting list has not arrived yet. A useful editor distinguishes waiting, missing data and a failed request, and tells the user what to do next.
“Nothing here yet” is different from “nothing exists”
Treat “not loaded yet” as its own state. An empty list before a request finishes is not evidence that the saved selection is unavailable.
I expect separate states for not started, loading, loaded with results, loaded without results and failed. A warning about a missing option needs a completed lookup; a timeout should offer a retry rather than declare that the option has disappeared.
Clear the whole dependent selection
Linked fields need the same care. Pick a broad option, then a narrower option, then an individual item. If changing the first field clears only part of what follows it, old selections can remain in the saved attributes while the screen is already showing a new list.
Make the reset follow the dependency chain. Changing a parent should clear the children that no longer apply, their temporary lists and any error attached to the old combination. I test the submitted values as well as the visible labels.
What I ask of a good error message
- Say which action failed: loading a list, validating a choice or saving the block.
- Use language an editor understands, with technical detail available separately.
- Give a sensible next step, such as retrying the request or choosing again.
- Disappear when the condition has been resolved.
- Keep already saved content intact when a temporary service error occurs.
I test this with a slow connection, a failed request and an existing saved block, as well as the happy path of creating a new one. The awkward states are where an editor decides whether they trust the tool.
A useful final check is to ask someone to recover from a failed lookup without developer help. If they cannot tell whether to wait, retry or choose another value, the message or the recovery control still needs work.