From a5ee238a2aca7d68ee34d9a9a2096eed86496b53 Mon Sep 17 00:00:00 2001 From: Arc Date: Tue, 28 Jul 2026 13:52:56 +0000 Subject: [PATCH 1/3] docs(CSM-359): add publish usage details to billing page --- docs/account/my-organization/billing/index.md | 26 ++++++++++++++++++- 1 file changed, 25 insertions(+), 1 deletion(-) diff --git a/docs/account/my-organization/billing/index.md b/docs/account/my-organization/billing/index.md index e8ecb322..181c44ad 100644 --- a/docs/account/my-organization/billing/index.md +++ b/docs/account/my-organization/billing/index.md @@ -24,7 +24,7 @@ The Billing section allows you to monitor your usage summary, including builds, - **[Builds](/build/build-process-management/manual-builds)** : Number of builds initiated from the build module in a single billing cycle. - **[Code Push Updates](/code-push)** : The number of devices receiving CodePush updates within a single billing cycle. - **[Testing Distribution](/testing-distribution/testing-portal)** : Number of app downloads from the Testing Portal in a single billing cycle. -- **[Publishes](/publish-to-stores-module)** : Number of publishes initiated from the Publish module in a single billing cycle. +- **[Publishes](/publish-to-stores-module)** : Number of publishes initiated from the Publish module in a single billing cycle. For the operations that count against this number, see [Publish Usage Details](#publish-usage-details). - **[Enterprise App Store](/enterprise-app-store/enterprise-portal)** : Number of app downloads from the Enterprise App Store in a single billing cycle. - **[Team Members](/account/my-organization/profile-and-team/team-management)** : Number of team members allowed in a single organization. - **[Artifact Storage](/account/my-organization/artifacts)** : Total storage size for all the build and distribution artifacts across the platform. @@ -40,6 +40,30 @@ Please note that the module usage counts displayed here, such as builds, testing When the usage limits exceed 85% of the allocated quota, notification emails will be sent to the organization’s Owner and the Billing Manager. ::: +### Publish Usage Details + +A publish counts against your usage every time it runs from the beginning, so knowing which operations start a publish from scratch helps you plan your billing cycle. + +The following operations increase publish usage: + +- Restarting a publish with the **Restart** or **Play** button in the Appcircle dashboard, or with a restart call through the API. +- Starting the same publish again from the first step, either in the Appcircle dashboard or through the API. This is not a restart operation, but the publish runs from the beginning, so it counts as a new publish. + +In both cases, usage is counted only when the publish start event is received, which means the job must be picked up by a runner. Server-side components do not use a runner or a queue, so their usage is counted at the moment the operation is performed. The same rules apply: restarting a publish or starting it from the first step increases usage. + +The following operations do not increase publish usage: + +- Publish jobs that are not picked up by a runner and remain in the queue. They appear in the [Publish Report](/publish-module/publish-report) as a single item with the **Waiting** status. +- Publishes started from an intermediate step, because they continue from where they left off. +- Queued jobs that move to the **Canceled**, **Timed Out**, or **Stopped** status without ever being picked up. + +#### Publish Report and Usage + +The Publish Report lists every publish attempt, so an entry in the report does not always mean that your usage increased. + +- Waiting publishes appear in the Publish Report without affecting usage. If a waiting publish is canceled or times out before it starts, only its status is updated in the report and usage does not increase. +- Publishes started from an intermediate step update the status of the existing report item. No new item is added and usage does not increase. + ### Sub-Organization Usage The Billing page for a Sub-Organization displays the same summary metrics as the root organization, except for: From 6460ba89ae12ad909742e8a774f4bac0c1995a62 Mon Sep 17 00:00:00 2001 From: Arc Date: Tue, 28 Jul 2026 14:05:53 +0000 Subject: [PATCH 2/3] docs(CSM-359): move publish usage details under the publish usage item --- docs/account/my-organization/billing/index.md | 33 +++++++++---------- 1 file changed, 16 insertions(+), 17 deletions(-) diff --git a/docs/account/my-organization/billing/index.md b/docs/account/my-organization/billing/index.md index 181c44ad..114d6690 100644 --- a/docs/account/my-organization/billing/index.md +++ b/docs/account/my-organization/billing/index.md @@ -24,26 +24,10 @@ The Billing section allows you to monitor your usage summary, including builds, - **[Builds](/build/build-process-management/manual-builds)** : Number of builds initiated from the build module in a single billing cycle. - **[Code Push Updates](/code-push)** : The number of devices receiving CodePush updates within a single billing cycle. - **[Testing Distribution](/testing-distribution/testing-portal)** : Number of app downloads from the Testing Portal in a single billing cycle. -- **[Publishes](/publish-to-stores-module)** : Number of publishes initiated from the Publish module in a single billing cycle. For the operations that count against this number, see [Publish Usage Details](#publish-usage-details). -- **[Enterprise App Store](/enterprise-app-store/enterprise-portal)** : Number of app downloads from the Enterprise App Store in a single billing cycle. -- **[Team Members](/account/my-organization/profile-and-team/team-management)** : Number of team members allowed in a single organization. -- **[Artifact Storage](/account/my-organization/artifacts)** : Total storage size for all the build and distribution artifacts across the platform. -- **[Build Concurrency](/build/build-process-management/manual-builds)** : Number of builds that can run simultaneously. -- **[Build Time Limit](/build/build-process-management/manual-builds)** : Number of minutes allowed per build and publish before it is automatically cancelled with a timeout status. -- **[Machine Plan](/infrastructure/machine-plans)** : Indicates the Machine Plan assigned to the organization. - -:::info Usage Count -Please note that the module usage counts displayed here, such as builds, testing distribution, and publishes, represent the combined totals for the organization and its sub-organizations. -::: - -:::warning Limit Warnings -When the usage limits exceed 85% of the allocated quota, notification emails will be sent to the organization’s Owner and the Billing Manager. -::: +- **[Publish to Stores](/publish-to-stores-module)** : Number of publishes initiated from the Publish module in a single billing cycle. For the operations that count against this number, see [Publish Usage Details](#publish-usage-details). ### Publish Usage Details -A publish counts against your usage every time it runs from the beginning, so knowing which operations start a publish from scratch helps you plan your billing cycle. - The following operations increase publish usage: - Restarting a publish with the **Restart** or **Play** button in the Appcircle dashboard, or with a restart call through the API. @@ -64,6 +48,21 @@ The Publish Report lists every publish attempt, so an entry in the report does n - Waiting publishes appear in the Publish Report without affecting usage. If a waiting publish is canceled or times out before it starts, only its status is updated in the report and usage does not increase. - Publishes started from an intermediate step update the status of the existing report item. No new item is added and usage does not increase. +- **[Enterprise App Store](/enterprise-app-store/enterprise-portal)** : Number of app downloads from the Enterprise App Store in a single billing cycle. +- **[Team Members](/account/my-organization/profile-and-team/team-management)** : Number of team members allowed in a single organization. +- **[Artifact Storage](/account/my-organization/artifacts)** : Total storage size for all the build and distribution artifacts across the platform. +- **[Build Concurrency](/build/build-process-management/manual-builds)** : Number of builds that can run simultaneously. +- **[Build Time Limit](/build/build-process-management/manual-builds)** : Number of minutes allowed per build and publish before it is automatically cancelled with a timeout status. +- **[Machine Plan](/infrastructure/machine-plans)** : Indicates the Machine Plan assigned to the organization. + +:::info Usage Count +Please note that the module usage counts displayed here, such as builds, testing distribution, and publishes, represent the combined totals for the organization and its sub-organizations. +::: + +:::warning Limit Warnings +When the usage limits exceed 85% of the allocated quota, notification emails will be sent to the organization’s Owner and the Billing Manager. +::: + ### Sub-Organization Usage The Billing page for a Sub-Organization displays the same summary metrics as the root organization, except for: From ab1dbc2c1d12d431a9b283ea4382d032ba61a9a9 Mon Sep 17 00:00:00 2001 From: Arc Date: Tue, 28 Jul 2026 14:10:55 +0000 Subject: [PATCH 3/3] docs(CSM-359): keep usage summary list intact and move publish usage details below it --- docs/account/my-organization/billing/index.md | 29 +++++++++---------- 1 file changed, 14 insertions(+), 15 deletions(-) diff --git a/docs/account/my-organization/billing/index.md b/docs/account/my-organization/billing/index.md index 114d6690..0a984ce6 100644 --- a/docs/account/my-organization/billing/index.md +++ b/docs/account/my-organization/billing/index.md @@ -25,6 +25,20 @@ The Billing section allows you to monitor your usage summary, including builds, - **[Code Push Updates](/code-push)** : The number of devices receiving CodePush updates within a single billing cycle. - **[Testing Distribution](/testing-distribution/testing-portal)** : Number of app downloads from the Testing Portal in a single billing cycle. - **[Publish to Stores](/publish-to-stores-module)** : Number of publishes initiated from the Publish module in a single billing cycle. For the operations that count against this number, see [Publish Usage Details](#publish-usage-details). +- **[Enterprise App Store](/enterprise-app-store/enterprise-portal)** : Number of app downloads from the Enterprise App Store in a single billing cycle. +- **[Team Members](/account/my-organization/profile-and-team/team-management)** : Number of team members allowed in a single organization. +- **[Artifact Storage](/account/my-organization/artifacts)** : Total storage size for all the build and distribution artifacts across the platform. +- **[Build Concurrency](/build/build-process-management/manual-builds)** : Number of builds that can run simultaneously. +- **[Build Time Limit](/build/build-process-management/manual-builds)** : Number of minutes allowed per build and publish before it is automatically cancelled with a timeout status. +- **[Machine Plan](/infrastructure/machine-plans)** : Indicates the Machine Plan assigned to the organization. + +:::info Usage Count +Please note that the module usage counts displayed here, such as builds, testing distribution, and publishes, represent the combined totals for the organization and its sub-organizations. +::: + +:::warning Limit Warnings +When the usage limits exceed 85% of the allocated quota, notification emails will be sent to the organization’s Owner and the Billing Manager. +::: ### Publish Usage Details @@ -48,21 +62,6 @@ The Publish Report lists every publish attempt, so an entry in the report does n - Waiting publishes appear in the Publish Report without affecting usage. If a waiting publish is canceled or times out before it starts, only its status is updated in the report and usage does not increase. - Publishes started from an intermediate step update the status of the existing report item. No new item is added and usage does not increase. -- **[Enterprise App Store](/enterprise-app-store/enterprise-portal)** : Number of app downloads from the Enterprise App Store in a single billing cycle. -- **[Team Members](/account/my-organization/profile-and-team/team-management)** : Number of team members allowed in a single organization. -- **[Artifact Storage](/account/my-organization/artifacts)** : Total storage size for all the build and distribution artifacts across the platform. -- **[Build Concurrency](/build/build-process-management/manual-builds)** : Number of builds that can run simultaneously. -- **[Build Time Limit](/build/build-process-management/manual-builds)** : Number of minutes allowed per build and publish before it is automatically cancelled with a timeout status. -- **[Machine Plan](/infrastructure/machine-plans)** : Indicates the Machine Plan assigned to the organization. - -:::info Usage Count -Please note that the module usage counts displayed here, such as builds, testing distribution, and publishes, represent the combined totals for the organization and its sub-organizations. -::: - -:::warning Limit Warnings -When the usage limits exceed 85% of the allocated quota, notification emails will be sent to the organization’s Owner and the Billing Manager. -::: - ### Sub-Organization Usage The Billing page for a Sub-Organization displays the same summary metrics as the root organization, except for: