Apply all registered flows to a router.

Besides each flow’s own trigger route this installs the auto-resume catch-alls: any text, any callback payload, and photo, video, voice, audio, location and command updates. Two things follow, and both matter for a bot that has routes of its own — apply the registry LAST, after those routes.

• Patterns are ranked, so the catch-alls lose. on_text(Prefix("x")) and on_callback(Prefix("x:")) are more specific than the Prefix("") the registry adds, and the router picks the most specific match — the bot’s route still runs.
• Typed input routes are TAKEN OVER. A photo, video, voice, audio, location or plain command carries no pattern to rank, so the registry’s handler wins over one the bot registered for the same input type, and when no flow is waiting the update is dropped rather than passed on. A bot that needs its own on_photo alongside flows should start those flows from a command or callback trigger and handle the media itself.

Commands registered with on_command are exempt: they dispatch by exact name, so only an UNREGISTERED command reaches the flow’s command resume.

Call a registered flow from any handler

Cancel a specific flow instance by ID, without running its on_flow_exit hook. See cancel_flow_instance_for for the hook-running variant.

Cancel a specific flow instance by ID, running its on_flow_exit hook.

Cancel all flows for a user in a chat, without running their on_flow_exit hooks — those take a Context this variant has none of.

Use it from admin tooling, cron jobs and shutdown paths. From a handler prefer cancel_user_flows_for, which does run the hooks.

Cancel every flow the context’s user has running in this chat, running each flow’s on_flow_exit hook — this is what /cancel uses, and what a dialog relies on to take its live keyboard down.

Returns the cancelled instance ids. A hook that fails is reported through the flow’s own error handling; the instance is deleted either way.

Create a new empty flow registry

Re-execute the current step of a user’s running flow — the render side of a flow, without advancing it.

Unlike call_flow this never starts anything: a user with no running instance of name is left alone and False comes back. Pair it with telega.background_context to refresh what a user is looking at from a job that finished elsewhere.

Add a flow to the registry with a trigger

Register a flow without a trigger (for calling from handlers)

Register a cancel command that cancels all active flows for the user

Register a cancel command with a custom callback

Add a flow to the registry with a trigger and initial data

Create a router handler that starts a flow

Restrict a registered flow’s callback auto-resume to payloads accepted by filter. Auto-resume normally delivers a callback to the first waiting flow regardless of payload; with a filter, a press that belongs to another flow’s keyboard skips this one and reaches its real target. Used by the dialog engine, whose payloads are self-identifying (dlg:<dialog_id>:...).

Handle callback payloads that no waiting flow consumed. Handlers are tried in registration order; the first whose matches accepts the raw payload runs. Used by dialogs to answer presses on messages of already finished dialogs (otherwise the spinner hangs and the press is silently swallowed by the registry’s catch-all route).