@flowapt/flowiq-cli 0.3.5 → 0.3.6

package/README.md

@@ -199,6 +199,10 @@ flowiq bc resume <org_id> --campaign july-referrals --commit [--retry-failed]
   `helpdesk_messages`. Built for the `--python` fire-and-forget engine (which
   returns a `broadcastId` but has no CLI status log), but works for any broadcast
   id (dashboard sends included). `flowiq bc status <org> <broadcastId>`.
+- **Engine auto-routing (v0.3.6):** any `send --tag` of **more than 10** eligible
+  recipients **always uses the python engine** (a `>2000` tag routes there too).
+  Only a ≤10 send stays on the resumable per-row Node engine. `--python` forces
+  python at any size. (CSV per-row sends stay on Node — python takes uniform params.)
 - **`--python` engine (v0.3.4, `send --tag` only)**: hand the whole send to the
   **python `/meta-broadcast` endpoint** — the *same* sender the dashboard's "Python
   endpoint" toggle uses — via a staff-gated proxy (the master key stays server-side

package/TEAM-GUIDE.md

@@ -92,7 +92,7 @@ When you see it, run `npm i -g @flowapt/flowiq-cli` — a stale version also mea
 | Split a big id-list cohort into send-safe batch tags | `flowiq seg plan <org_id> --tag-prefix … --ids-file …` → `flowiq seg apply … --commit` |
 | Send to one batch tag | `flowiq bc send <org_id> --tag <batch-tag> --template … --body param1="Hi {{first_name}}" --commit` |
 | Send a broadcast whose template has an IMAGE header | Same as above — the image is automatic (the template's own header image). Override with `--header-media <public-image-url>` if needed. |
-| Send via the SAME engine as the dashboard's "Python" toggle | add `--python` to a `bc send --tag …` (fire-and-forget; python resolves the tag + sends + tracks; no CLI resume for this engine) |
+| Send via the SAME engine as the dashboard's "Python" toggle | add `--python` to a `bc send --tag …` (fire-and-forget; python resolves the tag + sends + tracks; no CLI resume for this engine). **Any tag send over 10 recipients uses python automatically.** |
 | Check how a broadcast is landing (read/delivered/sent/failed) | `flowiq bc status <org_id> <broadcastId>` (the `broadcastId` a `--python` send prints) |
 | Read a contact's chat | `flowiq m pull <contact_id>` then open the JSON |
 | Export an org's full chat history | `flowiq export chats <org_id>` |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@flowapt/flowiq-cli",
-  "version": "0.3.5",
+  "version": "0.3.6",
   "description": "Command-line tool for FlowIQ staff: round-trip agent prompts, questionnaires, fine-tuning, pin-board tasks, webhooks, templates, agent-updates, chat exports, and live agent testing without ever touching service-role credentials.",
   "type": "module",
   "bin": {

package/src/commands/broadcast.js

@@ -812,17 +812,29 @@ async function runTagPipeline(orgId, opts, { commitStage }) {
   if (template.url_button?.present && !buttonLiteral) aborts.push("template has a dynamic URL button — pass --button param1=<code>");
   if (aborts.length) { for (const a of aborts) console.error(`ABORT — ${a}`); process.exit(1); }
 
-  // --python: hand the whole send to the python /meta-broadcast engine (the same
-  // sender the dashboard's "Python endpoint" toggle uses) via the staff-gated
-  // proxy. Python resolves the tag + eligibility + sends fire-and-forget.
+  // ENGINE ROUTING (policy): any send of MORE THAN 10 recipients ALWAYS uses the
+  // python /meta-broadcast engine (the proven bulk sender). --python forces it at
+  // any size; only a ≤10 send stays on the resumable per-row Node engine.
+  const PYTHON_MIN = 10;
   if (opts.python) {
     return runPythonTagSend(orgId, { opts, tag, templateName, template, headerMedia, bodyLiterals, buttonLiteral, commitStage });
   }
 
-  // resolve the tag server-side (broadcast-safe recipients only)
+  // resolve the tag server-side (broadcast-safe recipients only). A >2000 tag
+  // 413s the Node resolver — that's by definition >10, so route straight to python.
   let resolved;
   try { resolved = await http.post("broadcast", { action: "resolve-tag", organization_id: orgId, tag }); }
-  catch (e) { console.error(`Tag resolution failed: ${e.message}`); if (e.body?.error) console.error(`  ${e.body.error}`); process.exit(1); }
+  catch (e) {
+    if (e.status === 413) {
+      console.log(`Tag "${tag}" has >2000 contacts → PYTHON engine (any send >${PYTHON_MIN} uses python).`);
+      return runPythonTagSend(orgId, { opts, tag, templateName, template, headerMedia, bodyLiterals, buttonLiteral, commitStage });
+    }
+    console.error(`Tag resolution failed: ${e.message}`); if (e.body?.error) console.error(`  ${e.body.error}`); process.exit(1);
+  }
+  if (resolved.recipients.length > PYTHON_MIN) {
+    console.log(`Tag "${tag}": ${resolved.recipients.length} sendable (>${PYTHON_MIN}) → PYTHON engine (any send >${PYTHON_MIN} uses python).`);
+    return runPythonTagSend(orgId, { opts, tag, templateName, template, headerMedia, bodyLiterals, buttonLiteral, commitStage });
+  }
   console.log(`Tag "${tag}" on ${resolved.organization_name}: ${resolved.tagged_total} contact(s), ${resolved.recipients.length} sendable, ${resolved.excluded.length} excluded (opt-out/archived/blocked).`);
   if (!resolved.recipients.length) { console.log("Nothing sendable under this tag."); return; }
 

package/src/index.js

@@ -391,7 +391,7 @@ export function run(argv) {
     .option("--button <k=v>", "with --tag: dynamic URL button param, e.g. --button param1=<short-code>", broadcastCmd.collectKV, {})
     .option("--campaign <name>", "campaign id / config file slug (default: CSV filename / tag)")
     .option("--header-media <url>", "header image/video/doc URL for a media-header template (default: the template's own stored image)")
-    .option("--python", "with --tag: send via the python /meta-broadcast engine (same as the dashboard's Python toggle; fire-and-forget, python-tracked)")
+    .option("--python", "with --tag: force the python /meta-broadcast engine (same as the dashboard's Python toggle). NOTE: any tag send >10 recipients ALWAYS uses python automatically")
     .option("--commit", "actually send (omit to dry-run)")
     .option("--yes", "skip the type-the-campaign-name confirm gate (CI)")
     .option("--force-remap", "ignore the saved mapping and rebuild interactively")