---
id: PLAY-2
family: RT-PLAY
level: core
profiles: [runtime, editor-client]
posture: normative-target
added: "1.0"
changed: "1.0"
source: https://flowdrop.io/spec/rules/rt-play/play-2
specification: FlowDrop Workflow Specification 1.0-draft
licence: CC BY 4.0
---

# PLAY-2 — Creating a session answers the same row the list publishes

*RT-PLAY (Part II) · level: core · profiles: runtime, editor-client · added in 1.0*

A client can insert a creation response straight into its list without re-fetching, which is what makes one shared row shape load-bearing rather than tidy.

## The rule

> **Normative.** This is the rule.
>
> 1. Creating a session answers `201` and reading one answers `200`, both under `{success, data}`, and in both cases `data` is exactly the row the session list publishes in its `data[]`: `id`, `workflowId`, `name`, `status`, `createdAt`, `updatedAt`, `metadata`, `executions`, `owner`, in that order.
>
> 2. `owner` is exactly `{id, name}`.
>
> 3. `createdAt` and `updatedAt` are ISO 8601 strings, never numeric timestamps.
>
> 4. `executions` is an empty list, not null, for a session that has never run.

## Related rules

- Names: PLAY-1

---

Rule identifiers are permanent and are never renumbered. This specification carries
no implementation status: each implementation publishes its own standing against
these rules. Licensed CC BY 4.0.