Running and replaying¶
Replay a recent run¶
Open Recent runs in the chat header. It lists the workflow's last 12 runs that you may view, newest first, with the message that started each one or what else started it:
- a chat message
- a trigger, with the event and the entity or form it fired on, when known
- a call from code
- a sub-workflow run, which points to the run that started it
Pick one and the office replays it.
Send a live turn¶
With the Execute session workflow permission, the chat has a message box. Send a message and the office:
- runs it as a turn in a FlowDrop session owned by you,
- waits for the turn to finish,
- shows the answer in the chat and replays the run it produced.
Messages can be up to 2000 characters. Later messages reuse the same session, so the workflow gets the earlier ones as history.
Each page load starts a new conversation. Opening one deletes your earlier office sessions on that workflow, with their messages; their runs stay. Sessions still running, and your sessions outside the office (for example the site chat), are left alone.
Personal data
The session stores each message and sends it again as history on later turns, so a guardrail inside the workflow only sees the current turn. To mask or refuse a message before it is stored, implement hook_flowdrop_office_turn_alter().
Questions from the workflow¶
When the workflow stops to ask you something (a FlowDrop interrupt), the chat shows the question. If the question has options, they appear as buttons. Your answer, typed or picked, goes back as the next turn and resumes the paused run.
For yes/no confirmations the office reads yes, y, yeah, yep, sure, ok, okay, confirm, true, 1, si, sí, ja as yes, the same words the FlowDrop chat processor accepts. Anything else counts as no.
Playback controls¶
| Control | Key | Does |
|---|---|---|
| Pause | Space | Pauses or resumes the replay |
| 1× | Cycles the speed: 1×, 2×, ½× | |
| See all | Zooms out to the whole building | |
| Present | P | Full-screen presentation mode: the office fills the screen and the chat stays as a narrow column. Esc leaves it. |
Keys do nothing while the focus is in a text field or on a button.
When something goes wrong¶
| Message | Cause |
|---|---|
| The previous message is still running. | A turn is still running in this session. Wait for it. |
| This conversation was closed... | The session was deleted, usually by the office open in another tab. Reload. |
| That question was already answered or has expired. | The interrupt is no longer pending. Reload. |
| The workflow failed on this message. | The turn threw an error. Details are in the site log under the flowdrop_office channel. |
| The server answered 504. (or another status) | The turn runs inside the request and took longer than PHP's max_execution_time or the web server's timeout. Raise them for slow models, or replay the run from Recent runs once it finishes. |