Skip to main content

Artifacts

The Artifacts section allows you to manage the logs, build outputs, and cache files generated by your build profiles.

Screenshot

Retention Period​

Build logs and artifacts are deleted based on a retention period, which depends on your plan:

  • Starter accounts can't manage the retention period. After 30 days, logs and artifacts will be automatically deleted.
  • Enterprise plan organization users can manage the retention period. They can set 30, 60, 90, 180, or 365 days for a retention period. Enterprise plans can also choose the never delete option and manage their artifacts manually.
Screenshot
caution

Only build and distribution artifacts are deleted in this section. Artifacts of the Enterprise App Store and the Store Submit published applications will not be deleted.

Build Cache​

The Artifacts section also allows you to manually clear cached files created during the build process. This helps resolve unexpected caching issues or reduce storage usage.

Screenshot
Cache Deletion Scope

Clearing caches from a main organization also removes all associated caches from its sub-organizations.

If you only want to remove caches for a specific sub-organization, make sure to perform the action within that sub-organization. This helps prevent unintended data removal across related organizations.

Clearing the cache only removes temporary build data. It does not affect build artifacts, logs, or published applications.

Permission Required

Only users with Manager or Owner roles in the build can use the Clean Build Caches feature. For more information, please refer to the Role Management documentation.

Cache Limit by Plan

The build cache limit shown on the screen is determined by your subscription plan. For example:

  • Starter: 5GB
  • Developer: 10GB
  • Professional: 20GB
  • Enterprise: 30GB
  • Self-hosted: Customizable (see the documentation)

For more detailed information on how to use Cache Pull and Cache Push in Appcircle builds, please refer to the following documentation:

Regularly clearing your build cache can help maintain a healthy and efficient build environment.

FAQ​

Why am I seeing a "cache limit exceeded" error even though my cache usage is not full?​

Even if your sub-organization has not used the entire cache limit, other sub-organizations or the main organization may have. The cache limit is shared across the entire organization.

To view the full cache usage and identify which part of the organization is consuming the cache, please visit the main organization.

Example:​

  • Your sub-organization may show low usage:

    Screenshot

  • But the main organization may show that the overall limit has been reached:

    Screenshot