{"version":"2.1.238","anchor":"artifact-publishing-names-your-plan-s-daily-limit-and-why-a-","canonical_anchor":"artifact-publishing-names-your-plan-s-daily-limit-and-why-a-","heading":"Artifact publishing names your plan's daily limit and why a fetch was blocked","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/artifact-publishing-names-your-plan-s-daily-limit-and-why-a-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Artifact publishing names your plan's daily limit and why a fetch was blocked\n\nHitting your plan's daily artifact limit now says so by name instead of a generic rate-limit error.\n\n**What**\n\nHitting your plan's daily cap on new artifacts or pushes is now reported as such, with copy naming the plan, instead of a generic rate-limit error. Other rate limits are retried after the delay the server asks for, capped at 30 seconds. Failures fetching content now say whether a proxy refused the connection (including a 407 auth challenge) or an allowlist blocked it.\n\n**Details**\n\n- The cap message reads \"daily new-artifact limit for your plan reached\".\n- Allowlist remediation text differs for cloud environments, remote sessions and the desktop app's network settings.\n- Reachable by anyone publishing artifacts.\n\n**Evidence**\n\n`daily new-artifact limit for your plan reached`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}