Skip to content

Add remote troubleshoot button to v1 run view task panel#2460

Open
morgan-wowk wants to merge 1 commit into
execution-action-buttonfrom
execution-action-button-v1
Open

Add remote troubleshoot button to v1 run view task panel#2460
morgan-wowk wants to merge 1 commit into
execution-action-buttonfrom
execution-action-button-v1

Conversation

@morgan-wowk

@morgan-wowk morgan-wowk commented Jun 25, 2026

Copy link
Copy Markdown

Description

Surfaces the optional Remote Troubleshoot action button in the v1 run-view task panel (TaskOverview). The button component and all of its behavior are introduced in the parent PR; this change only mounts it in the v1 task overview so both run-view implementations expose the action.

When a task node is selected, the button appears for executions in a problematic state — FAILED / CANCELLED / SYSTEM_ERROR immediately, or PENDING / QUEUED once the task has been in that status for 5 minutes. Clicking it opens a modal where the user can add context and submit a request to a configurable endpoint.

The feature is opt-in and OSS-friendly: it renders nothing unless window.__TANGLE_REMOTE_TROUBLESHOOT_ACTION__ is configured (see docs/remote-troubleshoot-action.md), so there is no visible change for default deployments.

This is wiring only — no new logic. TaskOverview now reads runId from the execution data and renders <RemoteTroubleshootButton> with the selected task's runId, executionId, taskName, and status, guarded on runId being present.

Related Issue and Pull requests

Type of Change

  • New feature

Checklist

  • I have tested this does not break current pipelines / runs functionality
  • I have tested the changes on staging

Screenshots (if applicable)

Test Instructions

  1. Configure the action before the app mounts (e.g. inline in index.html):
  2. Open a pipeline run in the v1 run view and select a task node.
  3. Confirm the button shows for a FAILED / CANCELLED / SYSTEM_ERROR task immediately, and for a PENDING / QUEUED task once it has been in that status for 5 minutes.
  4. Unset the global and confirm no button renders.

Additional Comments

No secrets or deployment-specific values are introduced — the endpoint URL and labels are entirely deploy-time configuration provided by the operator.

@github-actions

github-actions Bot commented Jun 25, 2026

Copy link
Copy Markdown

🎩 Preview

A preview build has been created at: execution-action-button-v1/f144aca

Copy link
Copy Markdown
Author

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

This stack of pull requests is managed by Graphite. Learn more about stacking.

@morgan-wowk morgan-wowk changed the base branch from execution-action-button to graphite-base/2460 July 10, 2026 20:08
@morgan-wowk morgan-wowk force-pushed the execution-action-button-v1 branch from d61a883 to 364e9a6 Compare July 10, 2026 20:09
@morgan-wowk morgan-wowk changed the base branch from graphite-base/2460 to execution-action-button July 10, 2026 20:09
@morgan-wowk morgan-wowk changed the base branch from execution-action-button to graphite-base/2460 July 10, 2026 20:17
@morgan-wowk morgan-wowk force-pushed the execution-action-button-v1 branch from 364e9a6 to bb1d986 Compare July 10, 2026 20:17
@morgan-wowk morgan-wowk changed the base branch from graphite-base/2460 to execution-action-button July 10, 2026 20:17
@morgan-wowk morgan-wowk changed the base branch from execution-action-button to graphite-base/2460 July 10, 2026 20:28
@morgan-wowk morgan-wowk force-pushed the execution-action-button-v1 branch from bb1d986 to 2efae65 Compare July 10, 2026 20:28
@morgan-wowk morgan-wowk changed the base branch from graphite-base/2460 to execution-action-button July 10, 2026 20:28
@morgan-wowk morgan-wowk requested a review from yuechao-qin July 10, 2026 20:37
@morgan-wowk morgan-wowk marked this pull request as ready for review July 10, 2026 20:37
@morgan-wowk morgan-wowk requested a review from a team as a code owner July 10, 2026 20:37

@yuechao-qin yuechao-qin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Author

Getting this error {"detail":"Method Not Allowed"}?

https://oasis.shopify.io/runs/019f4dd53e07b3c23c92?tophat_location=execution-action-button-v1%2F2efae65

image.png

​Taking a look - thanks. Maybe be something missing on staging backend.

@yuechao-qin yuechao-qin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

V1 tested and looks fine in staging.

@morgan-wowk morgan-wowk changed the base branch from execution-action-button to graphite-base/2460 July 10, 2026 21:58
@morgan-wowk morgan-wowk force-pushed the execution-action-button-v1 branch from 2efae65 to f144aca Compare July 10, 2026 21:58
@morgan-wowk morgan-wowk changed the base branch from graphite-base/2460 to execution-action-button July 10, 2026 21:58
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