conductor-oss/conductor · error · Error

Failed to fetch event data

Error message

Failed to fetch event data

What it means

Error "Failed to fetch event data" thrown in conductor-oss/conductor.

Source

Thrown at ui-next/src/pages/eventMonitor/EventMonitorDetail/Refresher/state/services.ts:65

};
export const fetchEventData = async ({
  pageType,
  authHeaders,
  eventName,
  timeRange,
}: RefreshMachineContext) => {
  if (!authHeaders) {
    throw new Error("authHeaders is not defined");
  }

  try {
    if (pageType === PageType.EVENT_LISTING) {
      return await fetchEventListingData(authHeaders);
    }
    return await fetchEventMonitorData(authHeaders, eventName, timeRange);
  } catch (error) {
    console.error("Error fetching event data:", error);
    throw new Error("Failed to fetch event data");
  }
};

View on GitHub (pinned to cf7c3e4a8a)

Solutions

1. Confirm authHeaders are passed into the refresh machine context before invoking fetchEventData.
2. Check server availability and the event monitor endpoints; the underlying error is logged to the console.
3. Retry after verifying network connectivity to the Conductor API.

When it happens

Trigger: Thrown at ui-next/src/pages/eventMonitor/EventMonitorDetail/Refresher/state/services.ts:65 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of conductor-oss/conductor@cf7c3e4a8a (2026-08-14). Data as JSON: /api/errors/37a76f35518be60d. Report an issue: GitHub.