workflow-stop-design
Design FastGPT Workflow Stops
Long-running workflows need a reliable way to stop without leaving stale state. This skill outlines a Redis-backed stop design, API flow, frontend option, and tests.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "workflow-stop-design" from https://skillstore.io/skills/labring-workflow-stop-design.md and its manifest at https://skillstore.io/api/skills/labring-workflow-stop-design/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "workflow-stop-design". Summarize the workflow stop lifecycle.
Expected outcome:
The workflow starts without a stop key. A stop request creates a Redis key with a 60 second TTL. The dispatcher polls Redis, stops before new nodes, and deletes the key when the workflow finishes.
Using "workflow-stop-design". Identify the main API behavior.
Expected outcome:
The stop API validates chat identifiers, reuses chat authorization, sets the Redis stop flag, waits up to five seconds, and returns success even if cleanup finishes later.
Using "workflow-stop-design". List the key tests to write.
Expected outcome:
- Set a stop flag and verify it is detected.
- Delete a stop flag and verify the workflow can continue.
- Wait for completion and handle timeout behavior.
- Send concurrent stop requests and confirm idempotent behavior.
Security Audit
SafeAll 75 static findings are false positives in this markdown design document. The external command alerts are code fences or TypeScript backticks, the filesystem alerts are normal import paths, and the reconnaissance alert is an appId log example.
Risk Factors
⚙️ External commands (72)
📁 Filesystem access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/labring-workflow-stop-design/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/labring-workflow-stop-design?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/labring-workflow-stop-design?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/labring-workflow-stop-design/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/labring-workflow-stop-design.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
labring. (2026). workflow-stop-design security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/labring-workflow-stop-design/audits/7BibTeX citation
@techreport{labring-labring-workflow-stop-design-2026,
author = {labring},
title = {workflow-stop-design security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/labring-workflow-stop-design/audits/7},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "workflow-stop-design security audit report (audit version 7)"
version: "unspecified"
type: report
authors:
- name: "labring"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/labring-workflow-stop-design/audits/7"
identifiers:
- type: other
value: "skillstore:labring-workflow-stop-design:audit:7"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Plan Backend Cancellation
Use the design to add Redis-backed stop checks to a FastGPT workflow dispatcher.
Define Stop API Behavior
Use the API section to align request schema, authorization, timeout behavior, and client expectations.
Create Workflow Stop Tests
Use the test strategy to cover stop flag creation, deletion, waiting, timeout, and concurrent requests.
Try These Prompts
Explain this workflow stop design in simple terms. Focus on Redis keys, TTL, cleanup, and the stop API.
Map this Redis-backed stop design to my service structure. Identify the files, helpers, and authorization points I need to update.
Review this workflow stop design for failure modes. Cover Redis errors, timeouts, concurrent stop requests, and stale stop flags.
Create an implementation plan for this FastGPT workflow stop design. Include backend changes, API behavior, frontend options, tests, and rollout checks.
Best Practices
- Authorize appId and chatId before writing any stop flag.
- Keep TTL, poll interval, and wait timeout explicit and tested.
- Clear timers and Redis stop keys in the workflow completion path.
Avoid
- Treating frontend abort as enough to stop backend workflow execution.
- Writing stop keys without a TTL or final cleanup step.
- Reporting detailed stop success when the backend only requested graceful cancellation.