Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
@@ -1,17 +1,17 @@
---
name: "custom-domain-rate-limit"
description: "Use this skill when a user is setting up a custom domain and the _acme-challenge TXT record value never appears in the Mintlify dashboard — the dashboard shows a loading spinner, a blank field, or the value keeps changing on each attempt. This is caused by a Let's Encrypt certificate issuance rate limit from repeated failed validation attempts."

Check warning on line 3 in .mintlify/assistant/skills/custom-domain-rate-limit/skill.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

.mintlify/assistant/skills/custom-domain-rate-limit/skill.mdx#L3

Don't put a space before or after a dash.

Check warning on line 3 in .mintlify/assistant/skills/custom-domain-rate-limit/skill.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

.mintlify/assistant/skills/custom-domain-rate-limit/skill.mdx#L3

In general, use active voice instead of passive voice ('is caused').
---

# Custom domain _acme-challenge value not appearing

When the `_acme-challenge` TXT record value never loads in the dashboard, the cause is almost always a Let's Encrypt rate limit. Let's Encrypt limits how many certificate requests can be made for the same domain in a short window. Deleting and re-adding the domain, or retrying a failed validation, counts as a new attempt. After several failed attempts, Let's Encrypt imposes a cooldown before a new challenge token can be generated.

Check warning on line 8 in .mintlify/assistant/skills/custom-domain-rate-limit/skill.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

.mintlify/assistant/skills/custom-domain-rate-limit/skill.mdx#L8

In general, use active voice instead of passive voice ('be made').

Check warning on line 8 in .mintlify/assistant/skills/custom-domain-rate-limit/skill.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

.mintlify/assistant/skills/custom-domain-rate-limit/skill.mdx#L8

In general, use active voice instead of passive voice ('be generated').

Tell the user to:

1. Wait 24-72 hours before retrying. The rate limit clears on its own.
2. Leave the domain entry as-is in the dashboard. Deleting and re-adding the domain triggers new certificate requests and can extend the wait.
3. Avoid refreshing or clicking retry. Additional attempts may extend the cooldown further.
3. Avoid refreshing or selecting retry. Additional attempts may extend the cooldown further.

Once the cooldown clears, the `_acme-challenge` TXT value appears automatically. The user can then add it to their DNS and complete validation as normal.

Expand Down
4 changes: 2 additions & 2 deletions .mintlify/assistant/skills/editor-reset/skill.mdx
Original file line number Diff line number Diff line change
@@ -1,19 +1,19 @@
---
name: "editor-reset"
description: "Use this skill when a user reports that the Mintlify web editor is broken, not loading properly, showing outdated or stale content, or is stuck after a GitHub sync. Also applies when the file tree fails to load or the editor appears frozen or unresponsive."

Check warning on line 3 in .mintlify/assistant/skills/editor-reset/skill.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

.mintlify/assistant/skills/editor-reset/skill.mdx#L3

In general, use active voice instead of passive voice ('is broken').

Check warning on line 3 in .mintlify/assistant/skills/editor-reset/skill.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

.mintlify/assistant/skills/editor-reset/skill.mdx#L3

In general, use active voice instead of passive voice ('is stuck').
---

# Reset the editor

A force reset usually fixes a web editor that is broken, showing stale content, or failing to load the file tree — especially after a Git sync. Resetting clears local editor state without affecting published docs or Git history.

Check warning on line 8 in .mintlify/assistant/skills/editor-reset/skill.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

.mintlify/assistant/skills/editor-reset/skill.mdx#L8

In general, use active voice instead of passive voice ('is broken').

Check warning on line 8 in .mintlify/assistant/skills/editor-reset/skill.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

.mintlify/assistant/skills/editor-reset/skill.mdx#L8

Don't put a space before or after a dash.

Walk the user through these steps:

1. Open the web editor at [app.mintlify.com](https://app.mintlify.com).
2. Click the settings button in the editor toolbar. It has a gear icon and no text label.
2. Select the settings button in the editor toolbar. It has a gear icon and no text label.
3. Scroll down to the **Reset Editor** section.
4. Click **Reset Editor**.
4. Select **Reset Editor**.

The editor reloads and re-syncs from the Git repository.

If the issue persists after resetting, it may indicate a deeper sync conflict — escalate to the support team.

Check warning on line 19 in .mintlify/assistant/skills/editor-reset/skill.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

.mintlify/assistant/skills/editor-reset/skill.mdx#L19

Don't put a space before or after a dash.
2 changes: 1 addition & 1 deletion credits.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,7 @@ Export your usage activity log to CSV for deeper analysis, reporting, or record-

1. Navigate to the [Usage](https://app.mintlify.com/settings/organization/usage) page in your dashboard.
2. Optionally, adjust the date range in the toolbar to change the period the export covers.
3. In the **Activity log** section, click **Export to CSV**.
3. In the **Activity log** section, select **Export to CSV**.
4. Mintlify emails you a download link when the export is ready. The link expires after 72 hours.

The exported CSV includes the date, product, and credits consumed for each event in the selected range.
Expand Down