Trigger paused docs #14664
Trigger paused docs #14664
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
WalkthroughThe pull request introduces a new section titled "Why is my trigger paused?" to the Changes
Possibly related PRs
Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (1)
docs-v2/pages/troubleshooting.mdx (1)
81-85: LGTM! Consider enhancing the section with more details.The new section effectively communicates the trigger pause policy and basic troubleshooting steps. However, consider the following enhancements for better user experience:
## Why is my trigger paused? -On the Free tier, Pipedream automatically disables sources with a 100% error rate in the past 5 days. +<Callout type="warning"> +On the Free tier, Pipedream automatically disables sources that experience a 100% error rate over the past 5 days. This helps prevent unnecessary resource usage from continuously failing workflows. +</Callout> -To troubleshoot, you can look at the errors in the [source](/sources/) logs, and may need to reconnect your account and reenable the source for it to run again. +To troubleshoot: +1. Check the errors in your [source](/sources/) logs to identify the root cause +2. Common fixes include: + - Reconnecting your account if authentication has expired + - Updating API keys if they're invalid + - Verifying the connected account has necessary permissions +3. After addressing the issue, re-enable the source to resume operation + +Consider upgrading to a [paid tier](https://pipedream.com/pricing) for additional reliability features and support.
There was a problem hiding this comment.
"Pipedream automatically disables sources with a 100% error rate in the past 5 days for accounts on the Free plan.
To troubleshoot, you can look at the errors in the source logs, and may need to reconnect your account and re-enable the source for it to run again. If the issue persists, please reach out in the community."
This pull request includes a small update to the
docs-v2/pages/troubleshooting.mdxfile. The change adds a new section to the troubleshooting documentation to explain why a trigger might be paused and how to resolve it.Documentation update:
docs-v2/pages/troubleshooting.mdx: Added a new section titled "Why is my trigger paused?" explaining the automatic disabling of sources with a 100% error rate on the Free tier and providing troubleshooting steps.Summary by CodeRabbit
New Features
Documentation