Workflow redeployment check optimization #2483
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Optimizes the workflow redeployment check to prevent unnecessary API calls. Previously, the
/api/workflows/[id]/statusendpoint was triggered by all state changes, including UI-only interactions like moving blocks or opening/closing tools. This PR introduces adeployment-signatureutility to ensure the check is only triggered when deployment-relevant properties of the workflow change, significantly reducing API call frequency.Type of Change
Testing
The changes have been verified through local testing and code review to ensure the
deployment-signatureaccurately reflects deployment-relevant changes and theuse-change-detectionhook triggers the status check only when necessary. Reviewers should focus on the logic withincreateDeploymentSignatureto confirm all UI-only properties (e.g., position, layout, expanded states, test values) are correctly excluded.Checklist
Screenshots/Videos