Skip to content

Document workflow run limit for hobby plans #5439

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

Closed
mintlify wants to merge 1 commit into from
Closed

Document workflow run limit for hobby plans #5439

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 3 additions & 1 deletion agent/workflows.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
---

<Info>
Workflows are in beta. They're currently free for all plans during the beta period. Workflow features, availability, and pricing are subject to change.
Workflows are in beta. Workflow features, availability, and pricing are subject to change.
</Info>

Workflows run the agent automatically on a schedule or on a push to a repository. Each workflow defines a prompt for the agent and a trigger for when to run it. Workflows support both GitHub and GitLab repositories.
Expand All @@ -15,6 +15,8 @@

Each workflow can run up to 50 times a day. Runs that fail do not count toward this limit.

Hobby plans are limited to 100 workflow runs per month. Runs that fail do not count toward this limit. If you reach your monthly limit, upgrade to a paid plan for unlimited workflow runs.

Check warning on line 18 in agent/workflows.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

agent/workflows.mdx#L18 

In general, use active voice instead of passive voice ('are limited').

<Tip>
Use workflows that run on a schedule to automate recurring tasks like publishing changelogs or checking for grammar and style issues.

Expand Down Expand Up @@ -221,7 +223,7 @@
```text
Review the diff from the last merged PR in `your-org/your-product` for changes to API endpoints, parameters, response shapes, or error codes.

Update the corresponding API specifications or pages in the docs to reflect the changes. Include updated parameter descriptions, type information, and examples where affected.

Check warning on line 226 in agent/workflows.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

agent/workflows.mdx#L226 

Did you really mean 'informat'?

Success criteria: All API specifications and pages are up to date with the changes in the product repository.

Expand All @@ -233,7 +235,7 @@

### Track translation lag

**Trigger:** Cron schedule `0 9 * * 3` (Wednesdays at 9:00 AM UTC)

Check warning on line 238 in agent/workflows.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

agent/workflows.mdx#L238 

Use 'cron' instead of 'Cron'.

Update the example language subdirectories (`es/`, `fr/`, `zh/`) to your actual language subdirectories.

Expand All @@ -252,7 +254,7 @@

### SEO and metadata audit

**Trigger:** Cron schedule `0 9 * * 1` (Mondays at 9:00 AM UTC)

Check warning on line 257 in agent/workflows.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

agent/workflows.mdx#L257 

Use 'cron' instead of 'Cron'.

```text
Audit all MDX files in the docs for SEO and metadata quality. Check for:
Expand Down Expand Up @@ -296,7 +298,7 @@

### Changelog with notifications

**Trigger:** Cron schedule `0 9 * * 1` (Mondays at 9:00 AM UTC)

Check warning on line 301 in agent/workflows.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

agent/workflows.mdx#L301 

Use 'cron' instead of 'Cron'.
**Context repos:** `your-org/your-product`
**Slack notifications:** `documentation` channel, `tech-writer` user

Expand Down
Loading