Mintplex-Labs/anything-llm · error · Error

Failed to publish agent flow: ${error.message}

Error message

Failed to publish agent flow: ${error.message}

What it means

Community Hub publisher for Agent Flows. The modal builds a payload (name, description, steps, tags, visibility) and calls CommunityHub.createAgentFlow; on success:false the API's error string is rethrown, caught, and shown as a toast with the raw error.message appended after the colon. The generic prefix therefore always carries the specific backend reason with it.

Source

Thrown at frontend/src/components/CommunityHub/PublishEntityModal/AgentFlows/index.jsx:41

    setIsSubmitting(true);
    try {
      const form = new FormData(formRef.current);
      const data = {
        name: form.get("name"),
        description: form.get("description"),
        tags: tags,
        visibility: "private",
        flow: JSON.stringify({
          name: form.get("name"),
          description: form.get("description"),
          steps: entity.steps,
          tags: tags,
          visibility: "private",
        }),
      };
      const { success, error, itemId } =
        await CommunityHub.createAgentFlow(data);
      if (!success) throw new Error(error);
      setItemId(itemId);
      setIsSuccess(true);
    } catch (error) {
      console.error("Failed to publish agent flow:", error);
      showToast(`Failed to publish agent flow: ${error.message}`, "error", {
        clear: true,
      });
    } finally {
      setIsSubmitting(false);
    }
  };

  const handleKeyDown = (e) => {
    if (e.key === "Enter" || e.key === ",") {
      e.preventDefault();
      const value = tagInput.trim();
      if (value.length > 20) return;
      if (value && !tags.includes(value)) {

View on GitHub (pinned to 3aec848f28)

Solutions

1. Read the full toast / console.error — the text after the colon is the API's actual rejection reason
2. Confirm you are authenticated to the Community Hub (connection/settings) and retry
3. Shorten the flow: fewer steps or smaller step configs if the serialized flow is very large
4. Fill every required form field (name, description) and ensure tags are valid before submitting

function validFlowPayload(form, entity, tags) {
  const name = form.get("name")?.trim();
  const description = form.get("description")?.trim();
  if (!name || !description) return { ok: false, reason: "name and description are required" };
  if (!entity?.steps?.length) return { ok: false, reason: "flow has no steps" };
  if (JSON.stringify(entity.steps).length > MAX_FLOW_BYTES) return { ok: false, reason: "flow too large" };
  return { ok: true };
}

catch (error) {
  console.error("Failed to publish agent flow:", error);
  showToast(`Failed to publish agent flow: ${error.message}`, "error", { clear: true });
  if (/unauthor|401|session/i.test(error.message)) openCommunityHubLogin();
}

When it happens

Trigger: createAgentFlow rejects: missing/invalid fields (empty name or description), steps failing server-side validation, flow JSON too large, duplicate published item name, Community Hub session missing/expired, or a backend/network failure (non-2xx).

Common situations: Publishing while not signed in to the Community Hub; very long step payloads making JSON.stringify(steps) huge; hub API changed after an upgrade; transient outage or rate limiting of the hub.

Related errors

• Failed to publish slash command: ${error.message}
• Failed to publish prompt: ${error.message}
• Failed to load available flows
• Failed to load flow
• Failed to import agent flow. ${e.message}

AI-assisted analysis of Mintplex-Labs/anything-llm@3aec848f28 (2026-08-18). Data as JSON: /api/errors/c104af722ddeec90. Report an issue: GitHub.