langgenius/dify · error · Error

${errorMessage} See ${managedProcess.logFilePath}.

Error message

${errorMessage} See ${managedProcess.logFilePath}.

What it means

Error "${errorMessage} See ${managedProcess.logFilePath}." thrown in langgenius/dify.

Source

Thrown at e2e/scripts/run-cucumber.ts:70

  errorMessage,
  managedProcess,
  url,
}: {
  errorMessage: string
  managedProcess: ManagedProcess
  url: string
}) => {
  let waiting = true
  try {
    await Promise.race([
      waitForUrl(url, 180_000, 1_000),
      waitForUnexpectedProcessExit(managedProcess, () => !waiting),
    ])
  } catch (error) {
    if (error instanceof Error && error.message.includes('exited before becoming ready'))
      throw error

    throw new Error(`${errorMessage} See ${managedProcess.logFilePath}.`)
  } finally {
    waiting = false
  }
}

const main = async () => {
  const { forwardArgs, full, headed, seed, seedOnly } = parseRunOptions(process.argv.slice(2))
  const startAgentBackendForRun = shouldStartManagedAgentBackend()
  const cucumberReportDir = path.join(e2eDir, 'cucumber-report')
  const logDir = path.join(e2eDir, '.logs')
  let apiProcess: ManagedProcess | undefined
  let celeryProcess: ManagedProcess | undefined
  let difyAgentProcess: ManagedProcess | undefined
  let middlewareStarted = false
  let shellctlProcess: ManagedProcess | undefined

  let cleanupPromise: Promise<void> | undefined
  const cleanup = async () => {

View on GitHub (pinned to ef8544b173)

When it happens

Trigger: Thrown at e2e/scripts/run-cucumber.ts:70 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of langgenius/dify@ef8544b173 (2026-08-12). Data as JSON: /api/errors/13e97c8bdb2384da. Report an issue: GitHub.