sfdx force:source:pull doesn't pull changes made in formula fields

[ghost]

Summary

force:source:pull doesn't pull changes from scratch org made in a formula of custom field and force:source:status doesn't recognize them as well

Steps To Reproduce:

1. created a new number custom field - CF1__c
2. created a new formula(number) custom field - CF2__c where I use CF1__c in the formula
3. Both pulled (force:source:pull) successfully
4. changed CF1__c API to CF1Test__c -> SF automatically updated API in the formula of CF2__c field
5. pull changes again

Expected result

force:source:pull pulls changes of both fields

Actual result

only CF1Test__c field is pulled and updated, changes inside the formula field CF2__c are not pulled

Additional information

Feel free to attach a screenshot.

SFDX CLI Version sfdx-cli/7.54.4-8ff9ba9cc5 win32-x64 node-v10.15.3

SFDX plugin Version @oclif/plugin-autocomplete 0.1.5 (core) @oclif/plugin-commands 1.2.3 (core) @oclif/plugin-help 2.2.3 (core) @oclif/plugin-not-found 1.2.3 (core) @oclif/plugin-plugins 1.7.9 (core) @oclif/plugin-update 1.3.9 (core) @oclif/plugin-warn-if-update-available 1.7.0 (core) @oclif/plugin-which 1.0.3 (core) @salesforce/sfdx-trust 3.0.7 (core) analytics 1.7.1 (core) generator 1.1.2 (core) salesforcedx 48.10.1 (core) ├─ @salesforce/sfdx-plugin-lwc-test 0.1.5 (core) ├─ salesforcedx-templates 48.8.0 (core) └─ salesforce-alm 48.10.0 (core)

sfdx-cli 7.54.4 (core)

OS and version: Win 10

[germangamboa95]

We are currently experiencing the same issue with various metadata objects. Our workaround has been to pull it down using sfdx force:source:retrieve -m then specifying the thing we want.

[uip-robot-zz]

This issue has been linked to a new work item: W-10081864

[github-actions[bot]]

We have determined that the issue you reported exists in code owned by another team that uses only the official support channels. To ensure that your issue is addressed, open an official Salesforce customer support ticket with a link to this issue. We encourage anyone experiencing this issue to do the same to increase the priority. We will keep this issue open for the community to collaborate on.