conductor-oss/conductor · error · Error
Failed to fetch event monitor data
Error message
Failed to fetch event monitor data
What it means
Error "Failed to fetch event monitor data" thrown in conductor-oss/conductor.
Source
Thrown at ui-next/src/pages/eventMonitor/EventMonitorDetail/Refresher/state/services.ts:30
eventName?: string,
timeRange?: number,
) => {
try {
if (eventName) {
let url = `event/execution/${eventName}`;
if (timeRange && timeRange > 0) {
url += `?from=${timeRange}`;
}
const data = await queryClient.fetchQuery([fetchContext.stack, url], () =>
fetchWithContext(url, fetchContext, { headers }),
);
return groupDataByMessageId(data);
}
} catch (error) {
console.error("Error fetching event monitor data:", error);
throw new Error("Failed to fetch event monitor data");
}
};
const fetchEventListingData = async (headers: AuthHeaders) => {
try {
if (headers) {
const data = await queryClient.fetchQuery(
[fetchContext.stack, EVENT_MONITOR_URL],
() => fetchWithContext(EVENT_MONITOR_URL, fetchContext, { headers }),
);
return data;
}
} catch (error) {
console.error("Error fetching event list data:", error);
throw new Error("Failed to fetch event list data");
}
};
export const fetchEventData = async ({View on GitHub (pinned to cf7c3e4a8a)
Solutions
- Check that the Conductor server is reachable and the event monitor detail endpoint returns data for the given event name and time range.
- Verify the auth headers are present and valid; a 401/403 from fetchWithContext surfaces as this generic error.
- Open the browser console for the logged underlying error ('Error fetching event monitor data:') to see the real HTTP status.
When it happens
Trigger: Thrown at ui-next/src/pages/eventMonitor/EventMonitorDetail/Refresher/state/services.ts:30 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/6e055d1276438c86.
Report an issue: GitHub.