docs: Add max active run limit troubleshooting

platform-enterprise_docs/administration/overview.md

@@ -1,7 +1,8 @@
 ---
 title: "Admin panel"
 description: "Overview of Seqera user and organization administration"
-date: "21 Apr 2023"
+date created: "2023-04-21"
+last updated: "2026-08-11"
 tags: [administration, users, workspaces, organizations]
 ---
 
@@ -33,6 +34,12 @@ You can only add existing users to an organization. You can't remove the last ow
 
 See [Members](../orgs-and-teams/organizations#members) for more information.
 
+### Quotas
+
+Each organization has usage quotas, such as the maximum number of pipeline runs that can be active (submitted or running) at the same time. In Seqera Platform Enterprise, your Seqera license defines these quotas. You can't view or edit them in the **Admin panel**. [Contact Seqera support](https://support.seqera.io) to review or change the quotas for your organizations.
+
+If a pipeline launch fails with `Limit of N running workflows reached`, see [Troubleshooting](../troubleshooting_and_faqs/troubleshooting#limit-of-n-running-workflows-reached).
+
 ## Workspaces
 
 The **Workspaces** tab lists all the workspaces in your account.

platform-enterprise_docs/orgs-and-teams/organizations.md

@@ -1,7 +1,8 @@
 ---
 title: "Organizations"
 description: "Manage organizations in Seqera Platform."
-date: "21 Apr 2023"
+date created: "2023-04-21"
+last updated: "2026-08-11"
 tags: [organizations, administration]
 ---
 
@@ -28,6 +29,10 @@ As an **organization owner**, access the organization page from the organization
 
 Open the **Settings** tab on the organization page, and select **Edit** in the **Edit Organization** row. Update the settings and select **Update** to save.
 
+:::note
+Organization usage quotas, such as the maximum number of concurrent active pipeline runs, aren't part of the organization settings. In Seqera Platform Enterprise, your Seqera license defines these quotas. See [Quotas](../administration/overview#quotas) for more information.
+:::
+
 ### Organization resource usage tracking
 
 Select **Usage overview** next to the organization and workspace selector drop-down to view a window with the following usage details:

platform-enterprise_docs/troubleshooting_and_faqs/troubleshooting.md

@@ -2,7 +2,7 @@
 title: "General"
 description: "Troubleshooting Seqera Platform"
 date created: "2023-04-23"
-last updated: "2026-07-16"
+last updated: "2026-08-11"
 tags: [troubleshooting, help]
 ---
 
@@ -52,6 +52,17 @@ The behavior of `sleep` commands in your Nextflow workflows depends on where the
 - In an `errorStrategy` block, Nextflow uses the Groovy sleep function, which takes its value in milliseconds.
 - In a process script block, that language's sleep binary or method is used. For example, [this bash script](https://docs.seqera.io/nextflow/metrics) uses the bash sleep binary, which takes its value in seconds.
 
+#### `Limit of N running workflows reached`
+
+This error occurs at launch when your organization reaches its quota of concurrent active pipeline runs. All runs in `SUBMITTED` or `RUNNING` status across the organization's workspaces count toward the quota. Your Seqera license sets the limit. The related error `Organizational quota limit fully restricts usage of running workflows` means the quota blocks all launches in the organization.
+
+To resolve:
+
+1. Cancel any runs stuck in `SUBMITTED` status. Active runs occupy quota until they complete or you cancel them.
+2. [Contact Seqera support](https://support.seqera.io) to raise the quota.
+
+Seqera Platform retrieves license changes when it next polls the license server, every 24 hours by default.
+
 #### Large number of batch job definitions
 
 Platform normally looks for an existing job definition that matches your workflow requirement. If nothing matches, it recreates the job definition. Use a bash script to clear job definitions. Tailor it to your needs, for example to deregister only job definitions older than a set number of days: