fix(blocks): resolve variable display in mothership resource preview

[waleedlatif1]

Summary

• Variables block showed empty assignments in mothership resource preview but worked on the actual canvas
• currentWorkflowId was read from URL params, which don't include workflowId in the mothership route
• Fall back to activeWorkflowId from the workflow registry for embedded contexts

Type of Change

• Bug fix

Testing

Tested manually

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 18, 2026 5:22pm

[cursor]

PR Summary

Low Risk
Low risk, localized change to ID resolution logic for embedded/preview routes; main risk is using the wrong workflow ID in edge cases where both URL params and registry state disagree.

Overview
Fixes workflow block previews in embedded/mothership routes by resolving currentWorkflowId from URL params or falling back to activeWorkflowId from the workflow registry (still using empty strings in sandbox mode).

This ensures downstream workflow-scoped queries (e.g., variable hydration and other block metadata lookups) receive a valid workflow ID even when workflowId is not present in the route.

^{Reviewed by Cursor Bugbot for commit 4efea0d. Configure here.}

[greptile-apps]

Greptile Summary

This PR fixes a bug where the Variables block showed empty assignments in the Mothership resource preview. The root cause was that currentWorkflowId was derived exclusively from URL params (params.workflowId), which are absent in the Mothership route — the fix falls back to activeWorkflowId from the workflow registry, with a final || '' guard to preserve the string type.

Confidence Score: 5/5

Safe to merge — minimal, targeted fix with no side effects on the existing canvas path.

Single-line change with a clear fallback chain; the previous type-widening concern from the thread is resolved by the || '' guard; no new P0/P1 findings identified.

No files require special attention.

Important Files Changed

Filename	Overview
apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/workflow-block/workflow-block.tsx	Moves currentWorkflowId derivation after useBlockVisual (which provides activeWorkflowId) and adds a registry fallback + empty-string guard to fix Mothership context; type-safe and correct.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[WorkflowBlock renders] --> B{isSandbox?}
    B -- Yes --> C[currentWorkflowId = '']
    B -- No --> D{params.workflowId available?}
    D -- Yes --> E[currentWorkflowId = params.workflowId]
    D -- No e.g. Mothership route --> F{activeWorkflowId from registry?}
    F -- Yes --> G[currentWorkflowId = activeWorkflowId]
    F -- No --> H[currentWorkflowId = '' disables workspace-scoped queries]
    C --> I[Pass to useWebhookInfo / useScheduleInfo / SubBlockRow]
    E --> I
    G --> I
    H --> I

Loading

_{Reviews (2): Last reviewed commit: "fix(blocks): narrow currentWorkflowId to..." | Re-trigger Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 4efea0d. Configure here.}