Flow overview.md#360
Conversation
Added description
added a section Make sure flow is not interrupted if contact sends any keyword in between the flow ( https://glific.github.io/docs/docs/FAQ/Make%20sure%20flow%20is%20not%20interrupted%20if%20contact%20sends%20any%20keyword%20in%20between%20the%20flow./) in it
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughDocumentation metadata in the Flow Overview is refreshed by updating the "Last Updated" timestamp from October 2025 to May 2026. This is a single-line change to the document header that indicates when the documentation was last reviewed or updated. Documentation metadata update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![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
🧹 Nitpick comments (4)
docs/3. Product Features/03. Flows/1. Flow Overview.md (4)
33-35: Prefer “and” over “+” for readability & searchabilityUsing the literal “+” inside list titles can hamper readability and keyword-based searching in docs engines.
Consider:- - **Run this flow in the background + Background Flows** : + - **Run this flow in the background and Background Flows** :
36-36: Fix list-item indentation (MD005)
markdownlintflagged this line because it’s indented by 3 spaces instead of 4, breaking the nested list structure.- - **Skip Validation** : Check this box while sending results … + - **Skip Validation** : Check this box while sending results …
91-91: Remove trailing punctuation from heading (MD026)Headings should not end with a period.
-## Make sure flow is not interrupted if contact sends any keyword in between the flow. +## Make sure flow is not interrupted if contact sends any keyword in between the flow
93-93: Tighten wording for clarityMinor grammar tweak for smoother reading.
-Select the `Ignore Keyword` check box from edit flow screen to make sure the flow should not be interrupted in between if user sends keyword of another flow. +Select the `Ignore Keyword` checkbox on the Edit-Flow screen to ensure the active flow is not interrupted when a user sends a keyword that belongs to another flow.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/3. Product Features/03. Flows/1. Flow Overview.md(2 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/3. Product Features/03. Flows/1. Flow Overview.md
36-36: Inconsistent indentation for list items at the same level
Expected: 4; Actual: 3
(MD005, list-indent)
91-91: Trailing punctuation in heading
Punctuation: '.'
(MD026, no-trailing-punctuation)
added one more section as Make a flow inactive
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
docs/3. Product Features/03. Flows/1. Flow Overview.md (2)
36-36: Fix list-item indentation to silence markdownlint MD005
markdownlintflags this line because it’s indented 3 spaces while the sibling list items under Edit use 4. Align it for consistent formatting.- - **Skip Validation** : Check this box while sending results that are generated dynamically (not pre-defined in the flow). This is helpful while using the [resume Flow API](https://api.glific.com/#89f5f6e6-9bdc-48c2-96c5-ad8c1f7a834b) and the flow doesn’t already have those results set up. It lets the flow continue without checking if those result fields were expected. + - **Skip Validation** : Check this box while sending results that are generated dynamically (not pre-defined in the flow). This is helpful while using the [resume Flow API](https://api.glific.com/#89f5f6e6-9bdc-48c2-96c5-ad8c1f7a834b) and the flow doesn’t already have those results set up. It lets the flow continue without checking if those result fields were expected.
91-91: Remove trailing period from the heading (markdownlint MD026)Headings should not end with punctuation. Dropping the period keeps style consistent.
-## Make sure flow is not interrupted if contact sends any keyword in between the flow. +## Make sure flow is not interrupted if contact sends any keyword in between the flow
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/3. Product Features/03. Flows/1. Flow Overview.md(2 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/3. Product Features/03. Flows/1. Flow Overview.md
36-36: Inconsistent indentation for list items at the same level
Expected: 4; Actual: 3
(MD005, list-indent)
91-91: Trailing punctuation in heading
Punctuation: '.'
(MD026, no-trailing-punctuation)
mahajantejas
left a comment
mahajantejas
left a comment
There was a problem hiding this comment.
There seems to be conflict between branches, so i am not able to merge this.
Can you pls re-look at this one and try again?
|
🚀 Deployed on https://deploy-preview-360--glific-docs.netlify.app |
SangeetaMishr
requested review from
Fawas003 and
mahajantejas
and removed request for
mahajantejas
|
@Fawas003 - Can you review this please. |
|
@SangeetaMishr I couldn't see any change other than the date, what i need to review specifically |
|
@Fawas003 It was a old PR which was already approved but due to some conflicts it didn't get merge to main, I took help from Priyanshu. You can go ahead and merge it for now. |
|
@SangeetaMishr review completed, but unable to merge. It seems like like you will have to update the branch |
5 participants
Added the below section into Flow Overview
https://glific.github.io/docs/docs/FAQ/Make%20sure%20flow%20is%20not%20interrupted%20if%20contact%20sends%20any%20keyword%20in%20between%20the%20flow./
Summary by CodeRabbit