FlowiseAI/Flowise · error · Error

${e}

Error message

${e}

What it means

Wraps any failure from ZepCloudVectorStore.fromDocuments() in the ZepCloud node init. Note the store is built with FakeEmbeddings because Zep Cloud auto-embeds server-side. `new Error(e)` flattens the underlying Zep Cloud client/LangChain error to a string.

Source

Thrown at packages/components/nodes/vectorstores/ZepCloud/ZepCloud.ts:116

            const finalDocs = []
            for (let i = 0; i < flattenDocs.length; i += 1) {
                if (flattenDocs[i] && flattenDocs[i].pageContent) {
                    finalDocs.push(new Document(flattenDocs[i]))
                }
            }
            const client = new ZepClient({
                apiKey: apiKey
            })
            const zepConfig = {
                apiKey: apiKey,
                collectionName: zepCollection,
                client
            }
            try {
                await ZepCloudVectorStore.fromDocuments(finalDocs, new FakeEmbeddings(), zepConfig)
                return { numAdded: finalDocs.length, addedDocs: finalDocs }
            } catch (e) {
                throw new Error(e)
            }
        }
    }

    async init(nodeData: INodeData, _: string, options: ICommonObject): Promise<any> {
        const zepCollection = nodeData.inputs?.zepCollection as string
        const zepMetadataFilter = nodeData.inputs?.zepMetadataFilter
        const credentialData = await getCredentialData(nodeData.credential ?? '', options)
        const apiKey = getCredentialParam('apiKey', credentialData, nodeData)

        const zepConfig: IZepCloudConfig & Partial<ZepFilter> = {
            apiKey,
            collectionName: zepCollection
        }
        if (zepMetadataFilter) {
            zepConfig.filter = typeof zepMetadataFilter === 'object' ? zepMetadataFilter : parseJsonBody(zepMetadataFilter)
        }
        zepConfig.client = new ZepClient({

View on GitHub (pinned to abe4a8601a)

Solutions

  1. Inspect the text after "Error:" for the flattened Zep Cloud error (auth, not-found, quota) and address it.
  2. Verify the Zep Cloud apiKey is current and has access to the project.
  3. Verify collectionName exists or can be auto-created in the Zep Cloud project.
  4. Confirm outbound connectivity to Zep Cloud.
  5. Patch the catch to rethrow e unchanged.

Example fix

// before
} catch (e) {
    throw new Error(e)
}

// after
} catch (e) {
    throw e instanceof Error ? e : new Error(String(e))
}
Defensive patterns

Strategy: try-catch

Validate before calling

// Pre-flight: verify Zep Cloud apiKey present + collection name non-empty
function validateZepCloudConfig(apiKey, collectionName) {
    if (!apiKey) throw new Error('Zep Cloud apiKey is required')
    if (!collectionName) throw new Error('Zep Cloud collectionName is required')
}

Type guard

null

Try / catch

try {
    await ZepCloudVectorStore.fromDocuments(finalDocs, new FakeEmbeddings(), zepConfig)
} catch (e) {
    throw e instanceof Error ? e : new Error(String(e))
}

Prevention

When it happens

Trigger: Invalid apiKey for Zep Cloud, collectionName missing or invalid, Zep Cloud API quota/throttling, network blocked to Zep Cloud endpoints, Zep client/SDK version mismatch.

Common situations: Wrong/revoked Zep Cloud API key; collectionName configured for a different project; FakeEmbeddings used but the project actually requires client-side embeddings (wrong node chosen); outbound network egress blocked.

Related errors

AI-assisted analysis of FlowiseAI/Flowise@abe4a8601a (2026-08-12). Data as JSON: /api/errors/7f6b9e16f3a96513. Report an issue: GitHub.