For any superbadge, you will have to install a package before starting. Copy the name of the package and use this command in the terminal.
$ sfdx force:source:retrieve -n NameOfThePackage
This will retrieve all the components in the package into a new folder named as the package.
Hope this helps.
You cannot activate/deactivate flows using Metadata API. Check limitation details here. However, previously flows were always deployed as inactive and now you can deploy a new active version of flow via Metadata API/Change sets and please note this setting doesn't appear in non-production orgs (such as scratch, sandbox, and developer orgs). Check more ...
For my case the above where not working, because I found that I had multiple sfdx folder due to installation from installer + npm :
I had one installed in the following path : C:\Users<>\AppData\Local\sfdx
and another one here : C:\Program Files\sfdx
The one installed via npm was at some point in time doing conflict with the other installation. I ...
In my Case the issue was that i had an EMPTY JSON-File in the User Home SFDX Directory. On Windows Machines:
There is also a Log-File "sfdx.log" which also gives detailled insight into the issue. In my Case there was a code line like this:
Use sfdx force:source:push rather than ...:deploy
Use sfdx force:source:pull rather than ...:retrieve
Then you can use sfdx force:source:status to see changes.
If you are using a Scratch Org, you should just be able to use the above commands.
If you are using a Sandbox, in your Dev Hub org you will need to go to Setup >> Dev Hub and check Enable ...
You can use diff against the org commands for a UI that shows changes from your org (in both directions!).
You can also see your current status from a terminal command:
Or you can deploy any changes that are detected in your workspace:
You can also go in to your Settings (File > Preferences > Settings &...