<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary Job Artifacts section on the right side of the page shows that there are artifacts to be downlaoded with the following message: > **Job artifacts** > > These artifacts are the latest. They will not be deleted (even if expired) until newer artifacts are available. However, there are actually none available to take action on. <!-- Summarize the bug encountered concisely. --> ### Steps to reproduce Run a pipeline that generates artifacts (See example) <!-- Describe how one can reproduce the issue - this is very important. Please use an ordered list. --> ### Example Project <!-- If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version. --> Refer to: https://gitlab.com/marcel.amirault/test-project/-/blob/master/.gitlab-ci.yml ### What is the current *bug* behavior? <!-- Describe what actually happens. --> Messaging is not correct, as there are no artifacts to download. ### What is the expected *correct* behavior? <!-- Describe what you should see instead. --> Do not show the **Job Artifacts** section at all, when none are available to Keep or Download ### Relevant logs and/or screenshots https://gitlab.com/marcel.amirault/test-project/-/jobs/896476708  <!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise. --> ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. -->