forcedotcom / forcedotcom/NextGeneration-DevOpsCenter

Environment shows "In Sync" after a failed Back Sync

Open
#49 3 comments 0 reactions 0 assignees View on GitHub
type:bug
Dominant language
No language data
Stars
7
Forks
1
PR merge metrics
No merged PRs in 30d

Description

The "Not in Sync" / "in Sync" badge shows the wrong information when the Back Sync failed, displaying "In Sync" even when the components failed to be deployed in the lower environment Target Org.

Image

Image

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the Environment sync-status badge and the Back Sync failure handling, then reproduce a failed deployment to a lower-environment Target Org. Done means the badge reports the environment as not in sync when Back Sync fails and components are not deployed.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.