UI doesn't provide details on dependency failure of CI pipeline

Summary

If a CI pipeline has an upward dependency, the job may fail of that dependency is no longer available. Though the CI job doesn't say WHAT that dependency is and the person triggering the job may be left at a loss as to what to do.

Steps to reproduce

Create a pipeline with cache that has a short expiration time. Try to execute a manual triggered job after the cache has expired.

What is the current bug behavior?

The UI doesn't provide any details as to why the job was unable to start. The message provided doesn't tell me anything actionable to recover from the problematic situation.

What is the expected correct behavior?

The UI should tell me that something expired, such as the cache dependency that was inadvertently configured to expire too early.

Output of checks

This bug happens on GitLab.com