> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Bitbucket on Vortex IQ > Monitor Bitbucket health, cost and reliability signals, and catch incidents and runaway spend early. Monitor Bitbucket health, cost and reliability signals, and catch incidents and runaway spend early. [Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=bitbucket) performance signals automated checks prepared fixes proven workflows API operations ### What you can achieve Capabilities are grouped around merchant outcomes, not API terminology. Improve discovery, conversion, campaigns and repeat purchase. Monitor orders, fulfilment, delivery and settlement. Find failures, leaks and risks before they cost sales. ### From connection to verified outcome The controlled sequence every capability follows. Nothing changes a connected system without the approval step. Authorise the source. Scopes are shown before access is granted. Watch the signals against your own baselines, not universal defaults. Run checks and gather evidence specific to your store. Explain what happened, why it matters and the proposed action. You review scope, risk and reversibility before anything changes. Apply through governed connector operations. Confirm the intended result and keep the receipt. No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls. ### Monitor performance 24 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system. | Signal | Alert behaviour | What it tracks | | ----------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Active Repos (30d)** | Watch only | Count of repos with updated\_on within the last 30d. | | **Avg Build Duration (30d)** | Watch only | Average build\_seconds\_used / 60 across completed pipelines (state.name=COMPLETED) with created\_on within the last 30d, across the top 10 repos. | | **Avg Comments / PR (30d)** | Watch only | Average comment\_count across PRs (state=OPEN or MERGED) updated within the last 30d; comment\_count is a native field on the pull request object. | | **Avg Commits / Active Repo (30d)** | Watch only | 30d commit count / active-repos-30d; concentration of delivery across the fleet. | | **Commits by Day (7d)** | Watch only | Commits grouped by calendar day over the last 7d (commit date field), summed across the top 10 repos. | | **Languages by Repo Count** | Watch only | Repos grouped by their language field (nulls skipped), top 10 by count. | | **Median Open PR Age** | Alert band 3 / 14 | Median of (now - created\_on) in days across all open PRs (state=OPEN); drives vc\_pr\_age\_days (lower is better). | | **Merged PRs (30d)** | Watch only | Count of PRs with state=MERGED and updated\_on within the last 30d (state=MERGED\&sort=-updated\_on) across the top 10 repos. | | **Most Active Repo (30d)** | Watch only | The repo with the most commits in the last 30d; value = commit count, detail = repo full\_name. | | **Open Pull Requests** | Watch only | Count of open PRs from /repositories/{workspace}/{repo_slug}/pullrequests?state=OPEN across the top 10 repos. | | **PR Age Alert** | Alert band 3 / 14 | Median open-PR age in days; fires when it crosses the vc\_pr\_age\_days band (bad at >14d). | | **Pipeline Runs (30d)** | Watch only | Count of pipeline runs with created\_on within the last 30d across the top 10 repos, from /repositories/{workspace}/{repo_slug}/pipelines/. | | **Pipelines Pass Rate (30d)** | Alert band 95 / 80 | Pipelines with state.result.name=SUCCESSFUL / all completed pipelines (state.name=COMPLETED) with created\_on within 30d, x100, across the top 10 repos | | **Private Repos** | Watch only | Count of repos with is\_private=true / total repos, x100. | | **Repos with Wiki Enabled** | Watch only | Count of repos with has\_wiki=true / total repos, x100 (native boolean field on the repository object). | | **Repositories** | Watch only | Count of repos returned by /repositories/{workspace} (pagelen=100). | | **Stale PRs (>14d)** | Watch only | Count of open PRs (state=OPEN) whose age (now - created\_on) exceeds 14 days. | | **Total Repo Size** | Watch only | Sum of the size field (bytes) across all repos from /repositories/{workspace}, converted to MB (divide by 1,048,576). | | Signal | Alert behaviour | What it tracks | | ------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Commits (30d)** | Alert band 0 / -50 | Count of commits from /repositories/{workspace}/{repo_slug}/commits (commit date within 30d) summed across the top 10 most-recently-updated repos; cha | | **Deploy Cadence (30d)** | Alert band 0 / -50 | 30d total delivery events (commits + merged PRs); value = 30d total, change\_pct vs the prior 30d drives vc\_deploy\_cadence. | | **Deploy Stall Alert** | Alert band 0 / -50 | Delivery-event (commits + merged PRs) change\_pct vs the prior 30d; fires on a stall per the vc\_deploy\_cadence band. | | **Pipeline Health Score** | Alert band 90 / 70 | 0-100 composite = 0.4 x Pipelines pass rate (30d) + 0.3 x PR-age score (100 at \<=3d open-PR median age, 0 at >=14d) + 0.3 x deploy-cadence score | | Signal | Alert behaviour | What it tracks | | -------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------- | | **Declined PRs (30d)** | Watch only | Count of PRs with state=DECLINED and updated\_on within the last 30d across the top 10 repos. | | **Failed Pipelines (30d)** | Watch only | Count of pipelines with state.result.name in (FAILED, ERROR) and created\_on within the last 30d across the top 10 repos. | ### Audit risks and opportunities A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. Open a check for the detail. **Severity** high · **Outcome** Run operations · **Fix status** Report only More than 1 in 5 CI runs is failing. At this rate, a genuinely broken change is more likely to slip through unnoticed (lost in the normal noise of failures) and developers waste time re-running or diagnosing failures that have nothing to do with their own change, slowing the whole team down. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `VC-CI-001` **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only Deploys or merges have dropped by more than half compared to the prior period. That usually means fixes and improvements, including fixes for issues this same audit has flagged elsewhere, are not shipping, which slows the whole team's ability to respond to anything urgent. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `VC-CADENCE-001` **Severity** medium · **Outcome** Run operations · **Fix status** Report only Half of open pull requests have been waiting more than two weeks. Work that is done but not merged is not delivering any value yet, and the longer a PR sits open, the more it tends to drift from the main branch, making it harder to merge later than it would have been today. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `VC-PR-001` #### Build your own automated fixes Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change. ### Automate approved work Vortex IQ is integrated with **5 read** and **0 write** operations across repositorys, repositorycommits, repositorypipelines, repositorypullrequests, users on Bitbucket. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words. Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=bitbucket) #### Ready to build your first Bitbucket workflow Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build. | Resource | Read operations | Write operations | | ---------------------- | --------------- | ---------------- | | repositorys | 1 | 0 | | repositorycommits | 1 | 0 | | repositorypipelines | 1 | 0 | | repositorypullrequests | 1 | 0 | | users | 1 | 0 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.