Skip to content

Docs/csm 359 #18

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
oykukurtgoz wants to merge 3 commits into
base: develop
Choose a base branch
from
Open

Docs/csm 359 #18

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a5ee238
docs(CSM-359): add publish usage details to billing page
Jul 28, 2026
6460ba8
docs(CSM-359): move publish usage details under the publish usage item
Jul 28, 2026
ab1dbc2
docs(CSM-359): keep usage summary list intact and move publish usage …
Jul 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 23 additions & 1 deletion docs/account/my-organization/billing/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
- **[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).

@coderabbitai coderabbitai Bot Jul 29, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Align the metric description with the counting rules.

“Number of publishes initiated” implies every attempt counts, but the new section says waiting, intermediate-step, and never-picked-up jobs do not increase usage. Describe this as the number of publish operations counted toward usage, or explicitly qualify “initiated.”

Also applies to: 45-63

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/account/my-organization/billing/index.md` at line 27, Update the Publish
to Stores metric description and the related Publish Usage Details section to
clarify that the value counts only publish operations included in usage,
excluding waiting, intermediate-step, and never-picked-up jobs; avoid wording
that implies every initiated attempt is counted.

- **[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.
Expand All @@ -40,6 +40,28 @@ 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

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.

@coderabbitai coderabbitai Bot Jul 29, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Use one cancellation spelling consistently.

This page uses “cancelled” on Line 32 but “canceled” here. Prefer the product’s exact status label, Canceled, while keeping surrounding prose consistent.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~62-~62: Do not mix variants of the same word (‘canceled’ and ‘cancelled’) within a single text.
Context: ...ffecting usage. If a waiting publish is canceled or times out before it starts, only its...

(EN_EXACT_COHERENCY_RULE)

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/account/my-organization/billing/index.md` at line 62, Update the
waiting-publish sentence in the billing documentation to use the product’s exact
status label “Canceled,” replacing the inconsistent “canceled” spelling while
preserving the surrounding prose.

Source: Linters/SAST tools

- 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:
Expand Down