Skip to content

Resolve #1501: how Agent executions and the id for the agent execution in the agent execution page - #1503

Open
v1r3n wants to merge 4 commits into
mainfrom
harness/issue-1501-921cfd11
Open

Resolve #1501: how Agent executions and the id for the agent execution in the agent execution page#1503
v1r3n wants to merge 4 commits into
mainfrom
harness/issue-1501-921cfd11

Conversation

@v1r3n

@v1r3n v1r3n commented Aug 7, 2026

Copy link
Copy Markdown
Collaborator

Summary

Repository validation shows the existing implementation correctly switches the breadcrumb to “Agent Executions” and uses the /agentExecutions/:id route parameter as the displayed/copied agent execution ID, while preserving workflow breadcrumbs on /execution/:id.

@v1r3n

v1r3n commented Aug 7, 2026

Copy link
Copy Markdown
Collaborator Author

…tion

react-vis-timeline internally does require("vis-data/esnext"), whose
esnext/index.js has `export * from "./esm"` — a bare directory import
that Node's ESM resolver rejects. Since no test actually renders the
Timeline component, mock the package globally following the same
pattern used for @monaco-editor/react.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants