FlowDrop Workflow Specification 1.0-draft

An unknown workflow's schema is a bare error document

The rule

Normative: this is the rule
  1. A schema read for a workflow that does not exist answers 404 with the body {"error": "Workflow not found."}: one key, no success key, and the trailing full stop part of the literal.
  2. Absence is answered before anything else is read, so an unknown identifier never reaches the schema-version or entity-tag logic.

What it means

An unrecognised identifier is answered before the schema-version or entity-tag logic runs at all — there is no stored document to version or tag, so nothing downstream of the lookup is reached. The body carries only the one key, not the {success, error} envelope other doors on this API return: a caller that reads success to decide whether a response failed finds nothing there to read.

Example

Reading the schema of a workflow that does not exist404 — refused
GET /api/flowdrop/workflows/{id}/schema

{"error": "Workflow not found."}

The trailing full stop is part of the literal message, not punctuation added in transcription.

Rule identifiers are permanent and are never renumbered. Each implementation publishes its own standing against these rules; this specification does not.spec 1.0-draft · META-5 · changed in spec 1.0