Artifact quota limit details?

Ran into our organizations quota limit for artifacts. I went in to the repo responsible for generating the most artifacts and deleted the majority of the artifacts and also reduced the retention from 90 days to 30. From reading other posts from people in this same situation it seems like it might take a few hours for cleanup processes to work and update the quota. After 4 hours and many failed workflows due to artifact quota limit, the quota limit was still being hit. I was only able to reset the artifact quota limit by deleting old workflow runs. As soon as I did that we were able to get below our quota and workflows were successful again.

My questions:

  • What items count towards the artifact quota? Based on the scenario I described above, I am guessing that both artifacts and workflow logs count. I could not find anything in the Github API or Actions documentation with these details.
  • I know that you can look at the billing section of our account to see storage space used. Is there any other way to check how close we are to our quota limit? The only way to access the billing section is with admin access, which is limited to only a handful of folks in our org. I suspect this is the case for most enterprise organizations.
  • How come lowering the retention policy did not clean up existing artifacts? I am guessing based on querying the API that the new retention policy only affects artifacts created after the policy is updated. Details from an older artifact that I queried after updating the retention policy:
  "expired": false,
  "created_at": "2020-10-23T18:57:08Z",
  "updated_at": "2020-10-23T18:57:14Z",
  "expires_at": "2021-01-21T18:33:51Z"

Details from an artifact created after I updated the policy:

   "expired": false,
   "created_at": "2020-11-19T03:56:20Z",
   "updated_at": "2020-11-19T03:56:25Z",
   "expires_at": "2020-12-19T02:46:52Z"

FWIW we have a Github Enterprise account and all of our repos are private.

It would be helpful if all of these points were clarified in the documentation (I am happy to create a pull request to update the docs once I get updates on these things).