cli
cli copied to clipboard
Published
20 hours ago •
forcedotcom
forcedotcom
Unable to find type ExperienceResource in registry
Summary
When trying to deploy a single Permission Set, using sf project deploy command, I'm receiving an warning massage, and so that any chages hapens, the command seems to be stuck.
Steps To Reproduce
- Authenticate with an sandbox, using VSCode extension;
- So that run command sf project deploy start, trying to deploying a single Permission Set, using the alias of the connected sandbox, on step 1;
> sf project deploy start --target-org bv-int --source-dir .\force-app\main\default\permissionsets\Syste
mAdministration.permissionset-meta.xml --test-level NoTestRun --dry-run -w 10 --verbose
Expected result
Just validade the build of the Permission Set, checking sintax inside it, due to we are using dry-run flag.
Actual result
Command seems to be stuck, any response are given since, we get "Warning: Unable to find type ExperienceResource in registry" message.
PS C:\Users\renan.***\Workspace\sforce-sfdc-***> sf project deploy start --target-org bv-int --source-dir .\force-app\main\default\permissionsets\SystemAdministration.permissionset-meta.xml --test-level NoTestRun --dry-run -w 10 --verbose
Warning: Unable to find type ExperienceResource in registry
Warning: Unable to find type ExperienceResource in registry
Warning: Unable to find type ExperienceResource in registry
System Information
Which shell or terminal are you using? VSCode terminal (node); Full output of the sf version
{
"architecture": "win32-x64",
"cliVersion": "@salesforce/cli/2.21.8",
"nodeVersion": "node-v16.13.0",
"osVersion": "Windows_NT 10.0.19045",
"rootPath": "C:\\Users\\renan.***\\node\\node-v16.13.0-win-x64\\node_modules\\@salesforce\\cli",
"shell": "cmd.exe",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.0.2 (core)",
"@oclif/plugin-commands 3.0.7 (core)",
"@oclif/plugin-help 6.0.7 (core)",
"@oclif/plugin-not-found 3.0.4 (core)",
"@oclif/plugin-plugins 4.1.9 (core)",
"@oclif/plugin-search 1.0.8 (core)",
"@oclif/plugin-update 4.1.4 (core)",
"@oclif/plugin-version 2.0.8 (core)",
"@oclif/plugin-warn-if-update-available 3.0.5 (core)",
"@oclif/plugin-which 3.0.11 (core)",
"@salesforce/cli 2.21.8 (core)",
"apex 3.0.8 (core)",
"auth 3.0.10 (core)",
"data 3.0.5 (core)",
"deploy-retrieve 2.2.3 (core)",
"functions 1.21.11 (link) C:\\Users\\renan.***\\node\\node-v16.13.0-win-x64\\node_modules\\@salesforce\\plugin-functions",
"info 3.0.7 (core)",
"limits 3.0.5 (core)",
"marketplace 1.0.10 (core)",
"org 3.1.1 (core)",
"packaging 1.27.10 (core)",
"schema 3.0.8 (core)",
"settings 2.0.9 (core)",
"sobject 1.0.5 (core)",
"source 3.0.3 (core)",
"telemetry 3.1.4 (core)",
"templates 56.0.4 (core)",
"trust 3.1.2 (core)",
"user 3.1.0 (core)"
]
}
```json
### Additional information
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hello @renanlq :wave: None of the versions of sf you shared match the latest release.
Shared: 2.21.8
Latest: 2.22.7
Update to the latest version of Salesforce CLI (docs) and confirm that you're still seeing your issue.
You can also try the rc and nightly releases! (docs)
After updating, share the full output of sf version --verbose --json
Try to updated version.
@salesforce/cli version
PS C:\Users\renan.***\Workspace\sforce-sfdc-***> npm uninstall -g @salesforce/cli --force
npm WARN using --force Recommended protections disabled.
removed 1363 packages, and audited 1 package in 36s
found 0 vulnerabilities
PS C:\Users\renan.***\Workspace\sforce-sfdc-***> npm install -g @salesforce/cli --force
npm WARN using --force Recommended protections disabled.
added 1046 packages in 11m
124 packages are looking for funding
run `npm fund` for details
PS C:\Users\renan.***\Workspace\sforce-sfdc-***> sf version --verbose --json
{
"architecture": "win32-x64",
"cliVersion": "@salesforce/cli/2.21.8",
"nodeVersion": "node-v16.13.0",
"osVersion": "Windows_NT 10.0.19045",
"rootPath": "C:\\Users\\renan.***\\node\\node-v16.13.0-win-x64\\node_modules\\@salesforce\\cli",
"shell": "cmd.exe",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.0.2 (core)",
"@oclif/plugin-commands 3.0.7 (core)",
"@oclif/plugin-help 6.0.7 (core)",
"@oclif/plugin-not-found 3.0.4 (core)",
"@oclif/plugin-plugins 4.1.9 (core)",
"@oclif/plugin-search 1.0.8 (core)",
"@oclif/plugin-update 4.1.4 (core)",
"@oclif/plugin-version 2.0.8 (core)",
"@oclif/plugin-warn-if-update-available 3.0.5 (core)",
"@oclif/plugin-which 3.0.11 (core)",
"@salesforce/cli 2.21.8 (core)",
"apex 3.0.8 (core)",
"auth 3.0.10 (core)",
"data 3.0.5 (core)",
"deploy-retrieve 2.2.3 (core)",
"functions 1.21.11 (link) C:\\Users\\renan.***\\node\\node-v16.13.0-win-x64\\node_modules\\@salesforce\\plugin-functions",
"info 3.0.7 (core)",
"limits 3.0.5 (core)",
"marketplace 1.0.10 (core)",
"org 3.1.1 (core)",
"packaging 1.27.10 (core)",
"schema 3.0.8 (core)",
"settings 2.0.9 (core)",
"sobject 1.0.5 (core)",
"source 3.0.3 (core)",
"telemetry 3.1.4 (core)",
"templates 56.0.4 (core)",
"trust 3.1.2 (core)",
"user 3.1.0 (core)"
]
}
Even unistalling globaly, and instaling again, my version keeps: 2.21.8 I'll try to enforce version.
Hello @renanlq :wave: None of the versions of sf you shared match the latest release.
Shared: 2.21.8, 2.21.8
Latest: 2.22.7
Update to the latest version of Salesforce CLI (docs) and confirm that you're still seeing your issue.
You can also try the rc and nightly releases! (docs)
After updating, share the full output of sf version --verbose --json
Try to use @latest on install command
PS C:\Users\renan.***\Workspace\sforce-sfdc-***> npm install --global @salesforce/cli@latest
changed 1232 packages in 11m
124 packages are looking for funding
run `npm fund` for details
PS C:\Users\renan.***\Workspace\sforce-sfdc-***> sf version --verbose --json
{
"architecture": "win32-x64",
"cliVersion": "@salesforce/cli/2.21.8",
"nodeVersion": "node-v16.13.0",
"osVersion": "Windows_NT 10.0.19045",
"rootPath": "C:\\Users\\renan.***\\node\\node-v16.13.0-win-x64\\node_modules\\@salesforce\\cli",
"shell": "cmd.exe",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.0.2 (core)",
"@oclif/plugin-commands 3.0.7 (core)",
"@oclif/plugin-help 6.0.7 (core)",
"@oclif/plugin-not-found 3.0.4 (core)",
"@oclif/plugin-plugins 4.1.9 (core)",
"@oclif/plugin-search 1.0.8 (core)",
"@oclif/plugin-update 4.1.4 (core)",
"@oclif/plugin-version 2.0.8 (core)",
"@oclif/plugin-warn-if-update-available 3.0.5 (core)",
"@oclif/plugin-which 3.0.11 (core)",
"@salesforce/cli 2.21.8 (core)",
"apex 3.0.8 (core)",
"auth 3.0.10 (core)",
"data 3.0.5 (core)",
"deploy-retrieve 2.2.3 (core)",
"functions 1.21.11 (link) C:\\Users\\renan.***\\node\\node-v16.13.0-win-x64\\node_modules\\@salesforce\\plugin-functions",
"info 3.0.7 (core)",
"limits 3.0.5 (core)",
"marketplace 1.0.10 (core)",
"org 3.1.1 (core)",
"packaging 1.27.10 (core)",
"schema 3.0.8 (core)",
"settings 2.0.9 (core)",
"sobject 1.0.5 (core)",
"source 3.0.3 (core)",
"telemetry 3.1.4 (core)",
"templates 56.0.4 (core)",
"trust 3.1.2 (core)",
"user 3.1.0 (core)"
]
}
Any proxy configured on npm:
PS C:\Users\renan.***\Workspace\sforce-sfdc-***> npm config get proxy
null
Hello @renanlq :wave: None of the versions of sf you shared match the latest release.
Shared: 2.21.8, 2.21.8, 2.21.8
Latest: 2.22.7
Update to the latest version of Salesforce CLI (docs) and confirm that you're still seeing your issue.
You can also try the rc and nightly releases! (docs)
After updating, share the full output of sf version --verbose --json
Hello all!
I'm experiencing the same issue, even after updating sf to nightly release:
PS C:\Users\matheus.***\.workspace\git\sforce-sfdc-***> npm install --global @salesforce/cli@nightly
added 79 packages, removed 50 packages, changed 1097 packages, and audited 1457 packages in 8m
127 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
PS C:\Users\matheus.***\.workspace\git\sforce-sfdc-***> sf version --verbose --json
{
"architecture": "win32-x64",
"cliVersion": "@salesforce/cli/2.24.3",
"nodeVersion": "node-v16.13.0",
"osVersion": "Windows_NT 10.0.19045",
"rootPath": "C:\\Users\\matheus.***\\AppData\\Roaming\\npm\\node_modules\\@salesforce\\cli",
"shell": "cmd.exe",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.0.5 (core)",
"@oclif/plugin-commands 3.1.0 (core)",
"@oclif/plugin-help 6.0.10 (core)",
"@oclif/plugin-not-found 3.0.8 (core)",
"@oclif/plugin-plugins 4.1.15 (core)",
"@oclif/plugin-update 4.1.7 (core)",
"@oclif/plugin-version 2.0.11 (core)",
"@oclif/plugin-warn-if-update-available 3.0.9 (core)",
"@oclif/plugin-which 3.0.14 (core)",
"@salesforce/cli 2.24.3 (core)",
"apex 3.0.16 (core)",
"auth 3.1.2 (core)",
"data 3.0.14 (core)",
"deploy-retrieve 2.2.17 (core)",
"info 3.0.14 (core)",
"limits 3.1.1 (core)",
"marketplace 1.0.16 (core)",
"org 3.2.1 (core)",
"packaging 2.0.3 (core)",
"schema 3.1.0 (core)",
"settings 2.0.15 (core)",
"sobject 1.0.9 (core)",
"source 3.1.2 (core)",
"telemetry 3.1.9 (core)",
"templates 56.0.9 (core)",
"trust 3.3.1 (core)",
"user 3.2.1 (core)"
]
}
PS C:\Users\matheus.***\.workspace\git\sforce-sfdc-***> sf project deploy start -o int -m 'ApexClass:SerasaShareholdersRequestApiModel' -l RunLocalTests --dry-run
Warning: Unable to find type ExperienceResource in registry
Warning: Unable to find type ExperienceResource in registry
Warning: Unable to find type ExperienceResource in registry
Hi everyone,
I'd to make some changes from my network side, due to some blocks downloading the nightly version.
But now with the updated version:
PS C:\Users\renan.***\Workspace\sforce-sfdc-***> sf version --verbose --json
{
"architecture": "win32-x64",
"cliVersion": "@salesforce/cli/2.24.3",
"nodeVersion": "node-v16.13.0",
"osVersion": "Windows_NT 10.0.19045",
"rootPath": "C:\\Users\\renan.***\\node\\node-v16.13.0-win-x64\\node_modules\\@salesforce\\cli",
"shell": "cmd.exe",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.0.5 (core)",
"@oclif/plugin-commands 3.1.0 (core)",
"@oclif/plugin-help 6.0.10 (core)",
"@oclif/plugin-not-found 3.0.8 (core)",
"@oclif/plugin-plugins 4.1.15 (core)",
"@oclif/plugin-search 1.0.11 (core)",
"@oclif/plugin-update 4.1.7 (core)",
"@oclif/plugin-version 2.0.11 (core)",
"@oclif/plugin-warn-if-update-available 3.0.9 (core)",
"@oclif/plugin-which 3.0.14 (core)",
"@salesforce/cli 2.24.3 (core)",
"apex 3.0.16 (core)",
"auth 3.1.2 (core)",
"data 3.0.14 (core)",
"deploy-retrieve 2.2.17 (core)",
"functions 1.21.11 (link) C:\\Users\\renan.***\\node\\node-v16.13.0-win-x64\\node_modules\\@salesforce\\plugin-functions",
"info 3.0.14 (core)",
"limits 3.1.1 (core)",
"marketplace 1.0.16 (core)",
"org 3.2.1 (core)",
"packaging 2.0.3 (core)",
"schema 3.1.0 (core)",
"settings 2.0.15 (core)",
"sobject 1.0.9 (core)",
"source 3.1.2 (core)",
"telemetry 3.1.9 (core)",
"templates 56.0.9 (core)",
"trust 3.3.1 (core)",
"user 3.2.1 (core)"
]
}
Deploy:
PS C:\Users\renan.***\Workspace\sforce-sfdc-***> sf project deploy start --target-org bv-int --source-dir .\force-app\main\default\permissionsets\SystemAdministration.permissionset-meta.xml --test-level NoTestRun --dry-run -w 10 --verbose
Warning: Unable to find type ExperienceResource in registry
Warning: Unable to find type ExperienceResource in registry
Warning: Unable to find type ExperienceResource in registry
I'm not able to reproduce this running the same commands and the same CLI version as reported here. I used the Salesforce sample apps, dreamhouse-lwc and ebikes-lwc. I also used a project that contains the latest community metadata type, DigitalExperienceBundle since the ExperienceResource type is related to that. More specifically, ExperienceResource is a type that is not supported by the metadata API (for deploy/retrieve) but is used for server side source tracking purposes.
That said, it's just a warning that is being displayed and should not cause the command to hang. Here are some things to do:
- You are both using an old, unsupported NodeJS version (16.13.0) with your CLI install. Update to the current LTS version, 20.11.0 and install/use the CLI with it.
- When the command is running and appears stuck, open the org and check the deployment status. It could be that the deploy request is just spending a long time in the queue. This is (unfortunately) common after certain major releases like the one that just happened this past weekend that updated many sandbox instances.
- Run the command with debug output enabled. Do that by appending the
--dev-debugflag. Check the output for clues that could help reproduce the issue or explain what is happening. - There might be an
ExperienceResourceentry in one of the local source tracking files used by the CLI. If this is the case, delete the entry in that file (and post back here). This file exists in your project orgs directory and is called, "maxRevision.json". An example location would be something like, "<your_project_dir>/.sf/orgs/<org_id>/maxRevision.json"
Hi @shetzel,
Thanks for the feedback, so that I have tried some different commands, meanwhile, in order to not block our developments from our side we back to use sfdx cli, with same sf version intalled, for some orgs.
About the Community Experience Site, yes we have an old version that is running and commited in our git source, and due to we run Org Deployment, the metadata is inside our project sctructure. I'm checking now if any update about this sctructure is impacting the use of --source-dir our --metadata parameters.
Today I have tried again with sf cli, instead of using metadata I've used manifest, and any warning was triggeret when trying to validate our package on our Production Org (Release Winter'24):
PS C:\Users\renan.***\Workspace\sforce-sfdc-***> sf project deploy start --target-org prd --manifest .\manifest\package.xml --test-level RunLocalTests --dry-run -w 10 --verbose
Deploying (dry-run) v59.0 metadata to ***@***.br using the v59.0 SOAP API.
Deploy ID: 0A***AY
Status: In Progress | ████████████████████████████████████████ | 23/23 Components | 258/3534
So that when tring to use same command but in a Preview Sandbox (Release Spring '24):
PS C:\Users\renan.***\Workspace\sforce-sfdc-***> sf project deploy start --target-org bv-int --manifest .\manifest\package.xml --test-level RunLocalTests --dry-run -w 10 --verbose
Warning: Unable to find type ExperienceResource in registry
Warning: Unable to find type ExperienceResource in registry
Warning: Unable to find type ExperienceResource in registry
So that I noticed that the warning seems to be releated to the new Release that is comming Spring '24. We have created some cases to Salesforce, due to some OOTB resources (UI and Quick Actions ) that came with this new release, and we noticed in our Preveiw Sandbox. So that could you please evaluate the scenario comparing Lastet Release of org?
Add information, my version of Node and sf cli still the same.
And here the the deploy commnad with --dev-debug flag:
PS C:\Users\renan.***\Workspace\sforce-sfdc-***> sf project deploy start --target-org int --manifest .\manifest\package.xml --test-level RunLocalTests --dry-run -w 10 --verbose --dev-debug
find-root:root-plugin Finding root plugin using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\dist +0ms
find-root:root-plugin Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\dist +0ms
find-root:root-plugin Checking C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\dist\package.json +0ms
find-root:root-plugin Checking C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\package.json +0ms
find-root:root-plugin Found root by traversing up from starting point! +0ms
find-root:root-plugin Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
config:@salesforce/cli using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\oclif.manifest.json +0ms
config reading user plugins pjson C:\Users\renan.***\AppData\Local\sf\package.json +0ms
config loading plugins [
{
type: 'link',
name: '@salesforce/plugin-functions',
root: 'C:\\Users\\renan.***\\node\\node-v16.13.0-win-x64\\node_modules\\@salesforce\\plugin-functions'
}
] +13ms
config loading link plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\plugin-functions +0ms
config:@salesforce/plugin-functions using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\plugin-functions\oclif.manifest.json +0ms
config loading plugins [
'@oclif/plugin-autocomplete',
'@oclif/plugin-commands',
'@oclif/plugin-help',
'@oclif/plugin-not-found',
'@oclif/plugin-plugins',
'@oclif/plugin-search',
'@oclif/plugin-update',
'@oclif/plugin-version',
'@oclif/plugin-warn-if-update-available',
'@oclif/plugin-which',
'@salesforce/plugin-apex',
'@salesforce/plugin-auth',
'@salesforce/plugin-data',
'@salesforce/plugin-deploy-retrieve',
'@salesforce/plugin-info',
'@salesforce/plugin-limits',
'@salesforce/plugin-marketplace',
'@salesforce/plugin-org',
'@salesforce/plugin-packaging',
'@salesforce/plugin-schema',
'@salesforce/plugin-settings',
'@salesforce/plugin-sobject',
'@salesforce/plugin-source',
'@salesforce/plugin-telemetry',
'@salesforce/plugin-templates',
'@salesforce/plugin-trust',
'@salesforce/plugin-user'
] +38ms
find-root:@oclif/plugin-autocomplete Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@oclif/plugin-autocomplete Found starting point with require.resolve +0ms
find-root:@oclif/plugin-autocomplete Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-autocomplete\lib +0ms
find-root:@oclif/plugin-autocomplete Found root based on plugin name! +0ms
find-root:@oclif/plugin-commands Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@oclif/plugin-commands Found starting point with require.resolve +0ms
find-root:@oclif/plugin-commands Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-commands\lib +0ms
find-root:@oclif/plugin-commands Found root based on plugin name! +0ms
find-root:@oclif/plugin-help Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@oclif/plugin-help Found starting point with require.resolve +0ms
find-root:@oclif/plugin-help Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-help\lib +0ms
find-root:@oclif/plugin-help Found root based on plugin name! +0ms
find-root:@oclif/plugin-not-found Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@oclif/plugin-not-found Found starting point with require.resolve +0ms
find-root:@oclif/plugin-not-found Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-not-found\lib +0ms
find-root:@oclif/plugin-not-found Found root based on plugin name! +0ms
find-root:@oclif/plugin-plugins Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@oclif/plugin-plugins Found starting point with require.resolve +0ms
find-root:@oclif/plugin-plugins Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-plugins\lib +0ms
find-root:@oclif/plugin-plugins Found root based on plugin name! +0ms
find-root:@oclif/plugin-search Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@oclif/plugin-search Found starting point with require.resolve +0ms
find-root:@oclif/plugin-search Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-search\dist +0ms
find-root:@oclif/plugin-search Found root based on plugin name! +0ms
find-root:@oclif/plugin-update Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@oclif/plugin-update require.resolve could not find plugin starting point +0ms
find-root:@oclif/plugin-update Finding root using legacy method +0ms
find-root:@oclif/plugin-version Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@oclif/plugin-version Found starting point with require.resolve +0ms
find-root:@oclif/plugin-version Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-version\lib +0ms
find-root:@oclif/plugin-version Found root based on plugin name! +0ms
find-root:@oclif/plugin-warn-if-update-available Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@oclif/plugin-warn-if-update-available Found starting point with require.resolve +0ms
find-root:@oclif/plugin-warn-if-update-available Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-warn-if-update-available\lib +0ms
find-root:@oclif/plugin-warn-if-update-available Found root based on plugin name! +0ms
find-root:@oclif/plugin-which Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@oclif/plugin-which require.resolve could not find plugin starting point +0ms
find-root:@oclif/plugin-which Finding root using legacy method +0ms
find-root:@salesforce/plugin-apex Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@salesforce/plugin-apex Found starting point with require.resolve +0ms
find-root:@salesforce/plugin-apex Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-apex\lib +0ms
find-root:@salesforce/plugin-apex Found root based on plugin name! +0ms
find-root:@salesforce/plugin-auth Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@salesforce/plugin-auth Found starting point with require.resolve +0ms
find-root:@salesforce/plugin-auth Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-auth\lib +0ms
find-root:@salesforce/plugin-auth Found root based on plugin name! +0ms
find-root:@salesforce/plugin-data Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@salesforce/plugin-data Found starting point with require.resolve +0ms
find-root:@salesforce/plugin-data Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-data\lib +0ms
find-root:@salesforce/plugin-data Found root based on plugin name! +0ms
find-root:@salesforce/plugin-deploy-retrieve Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@salesforce/plugin-deploy-retrieve Found starting point with require.resolve +0ms
find-root:@salesforce/plugin-deploy-retrieve Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-deploy-retrieve\lib +0ms
find-root:@salesforce/plugin-deploy-retrieve Found root based on plugin name! +0ms
find-root:@salesforce/plugin-info Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@salesforce/plugin-info Found starting point with require.resolve +0ms
find-root:@salesforce/plugin-info Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-info\lib +0ms
find-root:@salesforce/plugin-info Found root based on plugin name! +0ms
find-root:@salesforce/plugin-limits Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@salesforce/plugin-limits Found starting point with require.resolve +0ms
find-root:@salesforce/plugin-limits Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-limits\lib +0ms
find-root:@salesforce/plugin-limits Found root based on plugin name! +0ms
find-root:@salesforce/plugin-marketplace Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@salesforce/plugin-marketplace Found starting point with require.resolve +0ms
find-root:@salesforce/plugin-marketplace Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-marketplace\lib +0ms
find-root:@salesforce/plugin-marketplace Found root based on plugin name! +0ms
find-root:@salesforce/plugin-org Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@salesforce/plugin-org Found starting point with require.resolve +0ms
find-root:@salesforce/plugin-org Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-org\lib +0ms
find-root:@salesforce/plugin-org Found root based on plugin name! +0ms
find-root:@salesforce/plugin-packaging Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@salesforce/plugin-packaging Found starting point with require.resolve +0ms
find-root:@salesforce/plugin-packaging Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-packaging\lib +0ms
find-root:@salesforce/plugin-packaging Found root based on plugin name! +0ms
find-root:@salesforce/plugin-schema Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@salesforce/plugin-schema Found starting point with require.resolve +0ms
find-root:@salesforce/plugin-schema Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-schema\lib +0ms
find-root:@salesforce/plugin-schema Found root based on plugin name! +0ms
find-root:@salesforce/plugin-settings Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@salesforce/plugin-settings Found starting point with require.resolve +0ms
find-root:@salesforce/plugin-settings Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-settings\lib +0ms
find-root:@salesforce/plugin-settings Found root based on plugin name! +0ms
find-root:@salesforce/plugin-sobject Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@salesforce/plugin-sobject Found starting point with require.resolve +0ms
find-root:@salesforce/plugin-sobject Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-sobject\lib +0ms
find-root:@salesforce/plugin-sobject Found root based on plugin name! +0ms
find-root:@salesforce/plugin-source Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@salesforce/plugin-source Found starting point with require.resolve +0ms
find-root:@salesforce/plugin-source Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-source\lib +0ms
find-root:@salesforce/plugin-source Found root based on plugin name! +0ms
find-root:@salesforce/plugin-telemetry Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@salesforce/plugin-telemetry Found starting point with require.resolve +0ms
find-root:@salesforce/plugin-telemetry Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-telemetry\lib +0ms
find-root:@salesforce/plugin-telemetry Found root based on plugin name! +0ms
find-root:@salesforce/plugin-templates Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@salesforce/plugin-templates Found starting point with require.resolve +0ms
find-root:@salesforce/plugin-templates Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-templates\lib +0ms
find-root:@salesforce/plugin-templates Found root based on plugin name! +0ms
find-root:@salesforce/plugin-trust Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@salesforce/plugin-trust Found starting point with require.resolve +0ms
find-root:@salesforce/plugin-trust Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-trust\lib +0ms
find-root:@salesforce/plugin-trust Found root based on plugin name! +0ms
find-root:@salesforce/plugin-user Finding root using C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli +0ms
find-root:@salesforce/plugin-user Found starting point with require.resolve +0ms
find-root:@salesforce/plugin-user Finding root starting at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-user\lib +0ms
find-root:@salesforce/plugin-user Found root based on plugin name! +0ms
find-root:@oclif/plugin-autocomplete Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-autocomplete +0ms
find-root:@oclif/plugin-commands Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-commands +0ms
find-root:@oclif/plugin-help Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-help +0ms
find-root:@oclif/plugin-not-found Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-not-found +0ms
find-root:@oclif/plugin-plugins Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-plugins +0ms
find-root:@oclif/plugin-search Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-search +0ms
find-root:@oclif/plugin-version Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-version +0ms
find-root:@oclif/plugin-warn-if-update-available Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-warn-if-update-available +0ms
find-root:@salesforce/plugin-apex Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-apex +0ms
find-root:@salesforce/plugin-auth Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-auth +0ms
find-root:@salesforce/plugin-data Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-data +0ms
find-root:@salesforce/plugin-deploy-retrieve Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-deploy-retrieve +0ms
find-root:@salesforce/plugin-info Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-info +0ms
find-root:@salesforce/plugin-limits Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-limits +0ms
find-root:@salesforce/plugin-marketplace Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-marketplace +0ms
find-root:@salesforce/plugin-org Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-org +0ms
find-root:@salesforce/plugin-packaging Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-packaging +0ms
find-root:@salesforce/plugin-schema Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-schema +0ms
find-root:@salesforce/plugin-settings Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-settings +0ms
find-root:@salesforce/plugin-sobject Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-sobject +0ms
find-root:@salesforce/plugin-source Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-source +0ms
find-root:@salesforce/plugin-telemetry Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-telemetry +0ms
find-root:@salesforce/plugin-templates Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-templates +0ms
find-root:@salesforce/plugin-trust Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-trust +0ms
find-root:@salesforce/plugin-user Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-user +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-autocomplete +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-commands +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-help +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-not-found +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-plugins +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-search +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-version +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-warn-if-update-available +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-apex +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-auth +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-data +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-deploy-retrieve +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-info +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-limits +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-marketplace +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-org +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-packaging +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-schema +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-settings +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-sobject +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-source +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-telemetry +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-templates +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-trust +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-user +0ms
find-root:@oclif/plugin-update Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-update +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-update +0ms
find-root:@oclif/plugin-which Found root at C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-which +0ms
config loading core plugin from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-which +0ms
config:@oclif/plugin-help using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-help\oclif.manifest.json +0ms
config:@oclif/plugin-commands using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-commands\oclif.manifest.json +0ms
config:@oclif/plugin-not-found using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-not-found\oclif.manifest.json +0ms
config:@oclif/plugin-autocomplete using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-autocomplete\oclif.manifest.json +0ms
config:@oclif/plugin-search using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-search\oclif.manifest.json +0ms
config:@oclif/plugin-version using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-version\oclif.manifest.json +0ms
config:@salesforce/plugin-auth using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-auth\oclif.manifest.json +0ms
config:@oclif/plugin-plugins using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-plugins\oclif.manifest.json +0ms
config:@oclif/plugin-warn-if-update-available using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-warn-if-update-available\oclif.manifest.j
son +0ms
config:@salesforce/plugin-deploy-retrieve using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-deploy-retrieve\oclif.manifest.json +0ms
config:@salesforce/plugin-apex using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-apex\oclif.manifest.json +0ms
config:@salesforce/plugin-info using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-info\oclif.manifest.json +0ms
config:@salesforce/plugin-org using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-org\oclif.manifest.json +0ms
config:@salesforce/plugin-limits using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-limits\oclif.manifest.json +0ms
config:@salesforce/plugin-marketplace using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-marketplace\oclif.manifest.json +0ms
config:@salesforce/plugin-schema using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-schema\oclif.manifest.json +0ms
config:@salesforce/plugin-packaging using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-packaging\oclif.manifest.json +0ms
config:@salesforce/plugin-settings using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-settings\oclif.manifest.json +0ms
config:@salesforce/plugin-telemetry using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-telemetry\oclif.manifest.json +0ms
config:@salesforce/plugin-data using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-data\oclif.manifest.json +0ms
config:@salesforce/plugin-source using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-source\oclif.manifest.json +0ms
config:@salesforce/plugin-templates using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-templates\oclif.manifest.json +0ms
config:@salesforce/plugin-sobject using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-sobject\oclif.manifest.json +0ms
config:@salesforce/plugin-trust using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-trust\oclif.manifest.json +0ms
config:@oclif/plugin-update using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-update\oclif.manifest.json +0ms
config:@oclif/plugin-which using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-which\oclif.manifest.json +0ms
config:@salesforce/plugin-user using manifest from C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-user\oclif.manifest.json +0ms
config config done +0ms
sf OS: +0ms
sf platform: win32 +0ms
sf architecture: x64 +1ms
sf release: 10.0.19045 +0ms
sf shell: cmd.exe +0ms
sf NODE: +0ms
sf version: 16.13.0 +1ms
sf CLI: +0ms
sf version: 2.24.3 +0ms
sf channel: stable +0ms
sf bin: sf +1ms
sf data: C:\Users\renan.***\AppData\Local\sf +0ms
sf cache: C:\Users\renan.***\AppData\Local\sf +0ms
sf config: C:\Users\renan.***\AppData\Local\sf +0ms
sf ENV: +1ms
sf SF_DEBUG: 1 +0ms
sf SF_ENV: development +0ms
sf SF_LOG_LEVEL: trace +1ms
sf NODE_OPTIONS: <not set> +0ms
sf SF_AUTOUPDATE_DISABLE: true +0ms
sf SF_BINPATH: <not set> +1ms
sf SF_COMPILE_CACHE: <not set> +0ms
sf SF_DISABLE_AUTOUPDATE: true +0ms
sf SF_INSTALLER: <not set> +1ms
sf SF_NPM_REGISTRY: <not set> +2ms
sf SF_REDIRECTED: <not set> +0ms
sf SF_UPDATE_INSTRUCTIONS: Use "npm update --global @salesforce/cli" to update npm-based installations. +2ms
sf ARGS: +1ms
sf 0: C:\Users\renan.***\node\node-v16.13.0-win-x64\node.exe +1ms
sf 1: C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\bin\run.js +0ms
sf 2: project +0ms
sf 3: deploy +1ms
sf 4: start +1ms
sf 5: --target-org +0ms
sf 6: int +0ms
sf 7: --manifest +1ms
sf 8: .\manifest\package.xml +0ms
sf 9: --test-level +0ms
sf 10: RunLocalTests +1ms
sf 11: --dry-run +0ms
sf 12: -w +0ms
sf 13: 10 +1ms
sf 14: --verbose +0ms
oclif:main process.execPath: C:\Users\renan.***\node\node-v16.13.0-win-x64\node.exe +0ms
oclif:main process.execArgv: +0ms
oclif:main process.argv: [
oclif:main 'C:\\Users\\renan.***\\node\\node-v16.13.0-win-x64\\node.exe',
oclif:main 'C:\\Users\\renan.***\\node\\node-v16.13.0-win-x64\\node_modules\\@salesforce\\cli\\bin\\run.js',
oclif:main 'project',
oclif:main 'deploy',
oclif:main 'start',
oclif:main '--target-org',
oclif:main 'int',
oclif:main '--manifest',
oclif:main '.\\manifest\\package.xml',
oclif:main '--test-level',
oclif:main 'RunLocalTests',
oclif:main '--dry-run',
oclif:main '-w',
oclif:main '10',
oclif:main '--verbose'
oclif:main ] +1ms
config start init hook +32ms
config:ts-node Skipping ts-node registration for C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-warn-if-update-available because NODE_ENV is NOT "test" or
"development" +0ms
config:ts-node Skipping ts-node registration for C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-settings because NODE_ENV is NOT "test" or "developme
nt" +11ms
config:ts-node Skipping ts-node registration for C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-update because NODE_ENV is NOT "test" or "development" +1m
s
sf:@salesforce/plugin-settings:hooks:init start (import) C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-settings\lib\hooks\init\load_config_meta.js +
0ms
config:ts-node Skipping ts-node registration for C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-deploy-retrieve because NODE_ENV is NOT "test" or "de
velopment" +66ms
sf:@salesforce/plugin-settings:hooks:init done +1s
sf:@oclif/plugin-update:hooks:init start (import) C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-update\dist\hooks\init.js +0ms
sf:@oclif/plugin-update:hooks:init done +1ms
sf:@oclif/plugin-warn-if-update-available:hooks:init start (import) C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\plugin-warn-if-update-available\lib\hooks\init
\check-update.js +0ms
sf:@oclif/plugin-warn-if-update-available:hooks:init done +11ms
config init hook done +2s
config runCommand project:deploy:start [ '--target-org', 'int', '--manifest', '.\\manifest\\package.xml', '--test-level', 'RunLocalTests', '--dry-run', '-w', '10', '--verbose' ] +1ms
config:ts-node Skipping ts-node registration for C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-deploy-retrieve because NODE_ENV is NOT "test" or "de
velopment" +1s
[15:03:51.255] TRACE (sf:core:config): Created 'sf:core:config' child logger instance
[15:03:51.255] TRACE (sf): Setup child 'sf:core:config' logger instance
config:@salesforce/plugin-deploy-retrieve (import) C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-deploy-retrieve\lib\commands\project\deploy\start.j
s +47s
config start prerun hook +45s
config:ts-node Skipping ts-node registration for C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli because NODE_ENV is NOT "test" or "development" +45s
config:ts-node Skipping ts-node registration for C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-telemetry because NODE_ENV is NOT "test" or "developm
ent" +2ms
sf:@salesforce/cli:hooks:prerun start (import) C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\dist\hooks\prerun.js +0ms
sf:@salesforce/cli:hooks:prerun done +1ms
sf:@salesforce/plugin-telemetry:hooks:prerun start (import) C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-telemetry\lib\hooks\telemetryPrerun.js +0m
s
sf:telemetry Usage acknowledgement file already exists +0ms
sf:telemetry Using telemetry logging file C:\Users\RENAN~1.QUE\AppData\Local\Temp\sf-telemetry\telemetry-aa4a902c6a1e05ae88ec4b48b1ca456b824b66bb.log +1ms
[15:04:36.630] TRACE (sf:Config): Created 'sf:Config' child logger instance
[15:04:36.630] TRACE (sf): Setup child 'sf:Config' logger instance
[15:04:36.631] TRACE (sf:Config): Created 'sf:Config' child logger instance
[15:04:36.631] TRACE (sf): Setup child 'sf:Config' logger instance
[15:04:36.631] DEBUG (sf:Config): Reading config file: C:\Users\renan.***\.sf\config.json because hasRead is false
[15:04:36.652] DEBUG (sf:Config): Reading config file: C:\Users\renan.***\Workspace\sforce-sfdc-***\.sf\config.json because hasRead is false
[15:04:36.772] TRACE (sf:OrgAccessor): Created 'sf:OrgAccessor' child logger instance
[15:04:36.772] TRACE (sf): Setup child 'sf:OrgAccessor' logger instance
[15:04:36.772] TRACE (sf:SandboxAccessor): Created 'sf:SandboxAccessor' child logger instance
[15:04:36.772] TRACE (sf): Setup child 'sf:SandboxAccessor' logger instance
[15:04:36.781] TRACE (sf:Org): Created 'sf:Org' child logger instance
[15:04:36.781] TRACE (sf): Setup child 'sf:Org' logger instance
[15:04:36.782] TRACE (sf:AuthInfoConfig): Created 'sf:AuthInfoConfig' child logger instance
[15:04:36.782] TRACE (sf): Setup child 'sf:AuthInfoConfig' logger instance
[15:04:36.782] TRACE (sf:crypto): Created 'sf:crypto' child logger instance
[15:04:36.783] TRACE (sf): Setup child 'sf:crypto' logger instance
[15:04:36.783] DEBUG (sf:crypto): retryStatus: undefined
[15:04:36.783] TRACE (sf:keyChain): Created 'sf:keyChain' child logger instance
[15:04:36.783] TRACE (sf): Setup child 'sf:keyChain' logger instance
[15:04:36.783] DEBUG (sf:keyChain): platform: win32
[15:04:36.797] DEBUG (sf:AuthInfoConfig): Reading config file: C:\Users\renan.***\.sfdx\renan.***.int.json because hasRead is false
[15:04:36.812] TRACE (sf:AuthInfo): Created 'sf:AuthInfo' child logger instance
[15:04:36.812] TRACE (sf): Setup child 'sf:AuthInfo' logger instance
[15:04:36.830] INFO (sf:AuthInfo): Returning fields for a connection using OAuth config.
[15:04:36.832] TRACE (sf:connection): Created 'sf:connection' child logger instance
[15:04:36.832] TRACE (sf): Setup child 'sf:connection' logger instance
[15:04:36.838] DEBUG (sf:connection): API version cache last checked on 05/01/2024 17:31:11 (now is 16/01/2024 15:04:36)
[15:04:36.838] DEBUG (sf:connection): Using cached API version: 59.0
[15:04:36.838] DEBUG (sf:connection): Connection created with apiVersion 59.0
[15:04:36.853] TRACE (sf:Org): Created 'sf:Org' child logger instance
[15:04:36.853] TRACE (sf): Setup child 'sf:Org' logger instance
[15:04:36.867] TRACE (sf:AuthInfoConfig): Created 'sf:AuthInfoConfig' child logger instance
[15:04:36.867] TRACE (sf): Setup child 'sf:AuthInfoConfig' logger instance
[15:04:36.868] TRACE (sf:crypto): Created 'sf:crypto' child logger instance
[15:04:36.868] TRACE (sf): Setup child 'sf:crypto' logger instance
[15:04:36.868] DEBUG (sf:crypto): retryStatus: undefined
[15:04:36.868] TRACE (sf:keyChain): Created 'sf:keyChain' child logger instance
[15:04:36.868] TRACE (sf): Setup child 'sf:keyChain' logger instance
[15:04:36.868] DEBUG (sf:keyChain): platform: win32
[15:04:36.868] DEBUG (sf:AuthInfoConfig): Reading config file: C:\Users\renan.***\.sfdx\renan.***.devcoe.json because hasRead is false
sf:telemetry Setting up process exit handler +137ms
sf:@salesforce/plugin-telemetry:hooks:prerun done +275ms
config prerun hook done +349ms
sf:project:deploy:start init version: @oclif/[email protected] argv: [ '--target-org', 'int', '--manifest', '.\\manifest\\package.xml', '--test-level', 'RunLocalTests', '--dry-run', '-w', '10', '--verbose' ] +0ms
[15:04:36.880] TRACE (sf:AuthInfo): Created 'sf:AuthInfo' child logger instance
[15:04:36.880] TRACE (sf): Setup child 'sf:AuthInfo' logger instance
[15:04:36.899] INFO (sf:AuthInfo): Returning fields for a connection using OAuth config.
[15:04:36.899] TRACE (sf:connection): Created 'sf:connection' child logger instance
[15:04:36.899] TRACE (sf): Setup child 'sf:connection' logger instance
[15:04:36.900] DEBUG (sf:connection): API version cache last checked on 1/15/2024, 6:08:15 PM (now is 16/01/2024 15:04:36)
[15:04:36.900] DEBUG (sf:connection): Using cached API version: 60.0
[15:04:36.900] DEBUG (sf:connection): Connection created with apiVersion 60.0
[15:04:36.905] TRACE (sf:Lifecycle): Created 'sf:Lifecycle' child logger instance
[15:04:36.905] TRACE (sf): Setup child 'sf:Lifecycle' logger instance
[15:04:36.905] DEBUG (sf:Lifecycle): 2 lifecycle events with the name sf:deploy have now been registered. When this event is emitted all 2 listeners will fire.
[15:04:36.907] TRACE (sf:Org): Created 'sf:Org' child logger instance
[15:04:36.907] TRACE (sf): Setup child 'sf:Org' logger instance
[15:04:36.907] TRACE (sf:AuthInfoConfig): Created 'sf:AuthInfoConfig' child logger instance
[15:04:36.907] TRACE (sf): Setup child 'sf:AuthInfoConfig' logger instance
[15:04:36.907] TRACE (sf:crypto): Created 'sf:crypto' child logger instance
[15:04:36.907] TRACE (sf): Setup child 'sf:crypto' logger instance
[15:04:36.907] DEBUG (sf:crypto): retryStatus: undefined
[15:04:36.908] TRACE (sf:keyChain): Created 'sf:keyChain' child logger instance
[15:04:36.908] TRACE (sf): Setup child 'sf:keyChain' logger instance
[15:04:36.908] DEBUG (sf:keyChain): platform: win32
[15:04:36.908] DEBUG (sf:AuthInfoConfig): Reading config file: C:\Users\renan.***\.sfdx\renan.***.int.json because hasRead is false
[15:04:36.912] TRACE (sf:AuthInfo): Created 'sf:AuthInfo' child logger instance
[15:04:36.912] TRACE (sf): Setup child 'sf:AuthInfo' logger instance
[15:04:36.927] INFO (sf:AuthInfo): Returning fields for a connection using OAuth config.
[15:04:36.928] TRACE (sf:connection): Created 'sf:connection' child logger instance
[15:04:36.928] TRACE (sf): Setup child 'sf:connection' logger instance
[15:04:36.928] DEBUG (sf:connection): API version cache last checked on 05/01/2024 17:31:11 (now is 16/01/2024 15:04:36)
[15:04:36.928] DEBUG (sf:connection): Using cached API version: 59.0
[15:04:36.928] DEBUG (sf:connection): Connection created with apiVersion 59.0
[15:04:36.943] TRACE (sf:Org): Created 'sf:Org' child logger instance
[15:04:36.943] TRACE (sf): Setup child 'sf:Org' logger instance
[15:04:36.958] TRACE (sf:AuthInfoConfig): Created 'sf:AuthInfoConfig' child logger instance
[15:04:36.958] TRACE (sf): Setup child 'sf:AuthInfoConfig' logger instance
[15:04:36.958] TRACE (sf:crypto): Created 'sf:crypto' child logger instance
[15:04:36.958] TRACE (sf): Setup child 'sf:crypto' logger instance
[15:04:36.958] DEBUG (sf:crypto): retryStatus: undefined
[15:04:36.958] TRACE (sf:keyChain): Created 'sf:keyChain' child logger instance
[15:04:36.958] TRACE (sf): Setup child 'sf:keyChain' logger instance
[15:04:36.958] DEBUG (sf:keyChain): platform: win32
[15:04:36.959] DEBUG (sf:AuthInfoConfig): Reading config file: C:\Users\renan.***\.sfdx\renan.***.devcoe.json because hasRead is false
[15:04:36.961] TRACE (sf:AuthInfo): Created 'sf:AuthInfo' child logger instance
[15:04:36.961] TRACE (sf): Setup child 'sf:AuthInfo' logger instance
[15:04:36.977] INFO (sf:AuthInfo): Returning fields for a connection using OAuth config.
[15:04:36.977] TRACE (sf:connection): Created 'sf:connection' child logger instance
[15:04:36.977] TRACE (sf): Setup child 'sf:connection' logger instance
[15:04:36.977] DEBUG (sf:connection): API version cache last checked on 1/15/2024, 6:08:15 PM (now is 16/01/2024 15:04:36)
[15:04:36.977] DEBUG (sf:connection): Using cached API version: 60.0
[15:04:36.977] DEBUG (sf:connection): Connection created with apiVersion 60.0
[15:04:36.979] TRACE (sf:SfProjectJson): Created 'sf:SfProjectJson' child logger instance
[15:04:36.979] TRACE (sf): Setup child 'sf:SfProjectJson' logger instance
[15:04:36.979] DEBUG (sf:SfProjectJson): Reading config file: C:\Users\renan.***\Workspace\sforce-sfdc-***\sfdx-project.json
[15:04:37.004] TRACE (sf:Org): Created 'sf:Org' child logger instance
[15:04:37.004] TRACE (sf): Setup child 'sf:Org' logger instance
[15:04:37.005] TRACE (sf:AuthInfoConfig): Created 'sf:AuthInfoConfig' child logger instance
[15:04:37.005] TRACE (sf): Setup child 'sf:AuthInfoConfig' logger instance
[15:04:37.005] TRACE (sf:crypto): Created 'sf:crypto' child logger instance
[15:04:37.005] TRACE (sf): Setup child 'sf:crypto' logger instance
[15:04:37.005] DEBUG (sf:crypto): retryStatus: undefined
[15:04:37.005] TRACE (sf:keyChain): Created 'sf:keyChain' child logger instance
[15:04:37.005] TRACE (sf): Setup child 'sf:keyChain' logger instance
[15:04:37.005] DEBUG (sf:keyChain): platform: win32
[15:04:37.005] DEBUG (sf:AuthInfoConfig): Reading config file: C:\Users\renan.***\.sfdx\renan.***.int.json because hasRead is false
[15:04:37.008] TRACE (sf:AuthInfo): Created 'sf:AuthInfo' child logger instance
[15:04:37.008] TRACE (sf): Setup child 'sf:AuthInfo' logger instance
[15:04:37.023] INFO (sf:AuthInfo): Returning fields for a connection using OAuth config.
[15:04:37.023] TRACE (sf:connection): Created 'sf:connection' child logger instance
[15:04:37.023] TRACE (sf): Setup child 'sf:connection' logger instance
[15:04:37.023] DEBUG (sf:connection): API version cache last checked on 05/01/2024 17:31:11 (now is 16/01/2024 15:04:37)
[15:04:37.023] DEBUG (sf:connection): Using cached API version: 59.0
[15:04:37.023] DEBUG (sf:connection): Connection created with apiVersion 59.0
[15:04:37.024] TRACE (sf:SourceTracking): Created 'sf:SourceTracking' child logger instance
[15:04:37.024] TRACE (sf): Setup child 'sf:SourceTracking' logger instance
[15:04:37.025] DEBUG (sf:SourceTracking): subscribing to predeploy/retrieve events
[15:04:37.025] DEBUG (sf:SourceTracking): subscribing to postdeploy/retrieve events
[15:04:37.025] TRACE (sf:SfProjectJson): Created 'sf:SfProjectJson' child logger instance
[15:04:37.025] TRACE (sf): Setup child 'sf:SfProjectJson' logger instance
[15:04:37.025] DEBUG (sf:SfProjectJson): Reading config file: C:\Users\renan.***\.sfdx\sfdx-project.json because hasRead is false
[15:04:37.042] TRACE (sf:componentSetBuilder): Created 'sf:componentSetBuilder' child logger instance
[15:04:37.042] TRACE (sf): Setup child 'sf:componentSetBuilder' logger instance
[15:04:37.042] DEBUG (sf:componentSetBuilder): Building ComponentSet from manifest: .\manifest\package.xml
[15:04:37.043] DEBUG (sf:componentSetBuilder): Searching in packageDir: C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\ for matching metadata
[15:04:37.052] TRACE (sf:ComponentSet): Created 'sf:ComponentSet' child logger instance
[15:04:37.052] TRACE (sf): Setup child 'sf:ComponentSet' logger instance
[15:04:37.052] TRACE (sf:ComponentSet): Created 'sf:ComponentSet' child logger instance
[15:04:37.052] TRACE (sf): Setup child 'sf:ComponentSet' logger instance
[15:04:37.052] DEBUG (sf:ComponentSet): Setting sourceApiVersion of 59.0 on ComponentSet from manifest
[15:04:37.053] TRACE (sf:MetadataResolver): Created 'sf:MetadataResolver' child logger instance
[15:04:37.053] TRACE (sf): Setup child 'sf:MetadataResolver' logger instance
[15:04:37.053] TRACE (sf:ComponentSet): Created 'sf:ComponentSet' child logger instance
[15:04:37.053] TRACE (sf): Setup child 'sf:ComponentSet' logger instance
[15:04:54.810] DEBUG (sf:componentSetBuilder): Matching metadata files (22):
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\classes\CaseAssignmenRulesFlow.cls
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\classes\CaseAssignmenRulesFlowTest.cls
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\classes\CaseDefaultTriggerHandler.cls
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\classes\CaseDefaultTriggerHandlerTest.cls
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\classes\CaseService.cls
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\classes\ProductService.cls
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\classes\ProductServiceTest.cls
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\classes\TelaUnicaController.cls
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\classes\TelaUnicaControllerTest.cls
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\applications\Atendimento.app-meta.xml
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\objects\Case\fields\ATD_Produtos__c.field-meta.xml
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\objects\Case\fields\PC_NuContratoOrigem__c.field-meta.xml
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\customMetadata\ATD_Parametrizacao.PIDCanalVoz.md-meta.xml
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\email\AtendimentoUnificadoFolder\Padrao.email
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\quickActions\Case.Email.quickAction-meta.xml
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\flexipages\ATD_Nao_Cliente.flexipage-meta.xml
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\flexipages\CaseAtendimentoUnificadoPage.flexipage-meta.xml
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\lwc\caseClosure
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\permissionsetgroups\AtendimentoOperacionalSAC.permissionsetgroup-meta.xml
[15:04:54.811] DEBUG (sf:componentSetBuilder): C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\permissionsetgroups\AtendimentoRenegociacao.permissionsetgroup-meta.xml
[15:04:54.811] DEBUG (sf:componentSetBuilder): (showing 20 of 22 matches)
[15:04:54.811] DEBUG (sf:componentSetBuilder): ComponentSet apiVersion = undefined
[15:04:54.811] DEBUG (sf:componentSetBuilder): ComponentSet sourceApiVersion = 59.0
[15:04:54.811] TRACE (sf:MetadataApiDeploy): Created 'sf:MetadataApiDeploy' child logger instance
[15:04:54.811] TRACE (sf): Setup child 'sf:MetadataApiDeploy' logger instance
[15:04:54.812] DEBUG (sf:SourceTracking): received scopedPreDeploy event
[15:04:54.812] DEBUG (sf:SourceTracking): ensureRemoteTracking: remote tracking does not exist yet; getting instance
[15:04:54.813] DEBUG (sf:connection): request
method: "GET"
url: "https://***--int.sandbox.my.salesforce.com/services/data/v59.0/tooling/sobjects/SourceMember/describe"
headers: {
"content-type": "application/json",
"user-agent": "sfdx toolbelt:"
}
[15:04:54.825] TRACE (sf:ShadowRepo): Created 'sf:ShadowRepo' child logger instance
[15:04:54.825] TRACE (sf): Setup child 'sf:ShadowRepo' logger instance
[15:04:54.826] TRACE (sf:ShadowRepo): start: getStatus (noCache = false)
[15:06:43.462] TRACE (sf:RemoteSourceTrackingService): Created 'sf:RemoteSourceTrackingService' child logger instance
[15:06:43.462] TRACE (sf): Setup child 'sf:RemoteSourceTrackingService' logger instance
[15:07:26.323] TRACE (sf:ShadowRepo): done: getStatus (noCache = false)
[15:07:26.323] TRACE (sf:ShadowRepo): start: getStatus (noCache = false)
[15:07:26.323] TRACE (sf:ShadowRepo): done: getStatus (noCache = false)
[15:07:26.347] DEBUG (sf:SourceTracking): ensureRemoteTracking: remote tracking already exists
[15:07:26.347] DEBUG (sf:RemoteSourceTrackingService): Query: SELECT MemberType, MemberName, IsNameObsolete, RevisionCounter FROM SourceMember WHERE RevisionCounter > 1754
[15:07:26.349] DEBUG (sf:connection): request
method: "GET"
url: "https://***--int.sandbox.my.salesforce.com/services/data/v59.0/tooling/query?q=SELECT%20MemberType%2C%20MemberName%2C%20IsNameObsolete%2C%20RevisionCounter%20FROM%20SourceMember%20WHERE%20RevisionCount
er%20%3E%201754"
headers: {
"content-type": "application/json",
"user-agent": "sfdx toolbelt:"
}
Warning: Unable to find type ExperienceResource in registry
Warning: Unable to find type ExperienceResource in registry
Warning: Unable to find type ExperienceResource in registry
I spend about 10 minutes waiting any change after Warning message, with no update from CLI side and sandbox Deployment Status page.
Hi @shetzel,
We have made some tests from our side, and the Warning message only appears with deployments running on preview sandbox Release Spring '24, due to we have refreshed one of our sandbox from Production, keeping Release Winter '24, and the deploy (--manifest, --source-dir or --metadata) command in this new sandbox does not reach the Warning message mentioned in this issue.
The warning messages are just warnings and should not cause the deploy to hang.
You can try setting SF_DISABLE_SOURCE_MEMBER_POLLING=true before the deploy to see if that improves things.
I would increase the command wait value to 60 to give it more time. When new major releases of Salesforce are rolled out it is common for things to take longer.
This doesn't appear to be a problem with the CLI. If you run the same command against the same sandbox (Spring '24) with an older version of the CLI I think it will take the same amount of time.
Hi @shetzel,
I understood about Warning messages usually not hang the deploy, but as I mentioned, only in Preview Sandbox this scenario is happening, seems to be something related to the new Release, and I keep the terminal opened after my last message, and the comand still in stucked in Warning message for more time, with any update from cli as TIMEOUT message, or Sandbox side, any new deploy Id with Failed or Canceled status on logs in Deployment Status page in my Sandbox. But we will try with a --wait with a high value ;)
Additionally We'll try to upate the config SF_DISABLE_SOURCE_MEMBER_POLLING=true, but it would be helpfull having an evaluate about why the same command and configurations (node and cli version) runs OK on Release Winter '24, but not in Release Spring '24 ?
In parallel we are searching for something inside Release Notes, that could help us about "ExperienceResource".
Sandbox Non-Preview with Release Winter '24:
PS C:\Users\renan.***\Workspace\sforce-sfdc-***> sf project deploy start --target-org stage --manifest .\manifest\package.xml --test-level RunLocalTests --dry-run -w 10 --verbose
Deploying (dry-run) v59.0 metadata to ***@***.br using the v59.0 SOAP API.
Deploy ID: 0A***bK
Status: In Progress | ████████████████████████████████████████ | 1/1 Components | 258/3512
Sandbox Preview with Release Spring '24:
PS C:\Users\renan.***\Workspace\sforce-sfdc-***> sf project deploy start --target-org int --manifest .\manifest\package.xml --test-level RunLocalTests --dry-run -w 10 --verbose
Warning: Unable to find type ExperienceResource in registry
Warning: Unable to find type ExperienceResource in registry
Warning: Unable to find type ExperienceResource in registry
I'll post sooner the full logs here, just to keep it logged here.
But now using --wait 360 just to garantee that my session keeps opened till we have any response.
Hi,
Sorry for being so anoying. I'm getting some more evidences to add here, full log from both sandboxes.
And, just to mention we are planing to open a case with Salesforce support, due to we already have 2 cases open due to new Release issues on Sandbox Preview, both cases has already open posts in trailhead: Spring '24 Voice Call Page UI Issue and 'Accept' button on cases not working in Spring 24, maybe this could be and issue from environment side, not cli as you mentioned.
By setting this: SF_DISABLE_SOURCE_MEMBER_POLLING=true I'm expecting the warning to no longer be displayed. However, I still think the deploy will hang or at least take much longer than usual.
why the same command and configurations (node and cli version) runs OK on Release Winter '24, but not in Release Spring '24 ?
That is not related to the CLI, but to server side changes and resource limitations when Salesforce major releases roll out.
You're best course of action right now is to open a case with Salesforce support about deploys to your sandbox being stuck, or at least taking much longer than normal.
Hi @shetzel,
Got an update about this topic, as you mentioned about the wait time, I'd increased the time an got a feedback, but after almost 2 hours after. :P
Sandbox Preview with Release Spring '24:
PS C:\Users\renan.***\Workspace\sforce-sfdc-***> sf project deploy start --target-org bv-int --source-dir .\force-app\main\default\permissionsets\SystemAdministration.permissionset-meta.xml --test-level RunLocalTests --dry-run -w 360 --verbose
Warning: Unable to find type ExperienceResource in registry
Warning: Unable to find type ExperienceResource in registry
Warning: Unable to find type ExperienceResource in registry
STATE FULL NAME TYPE FILE PATH
──────── ──────────────────── ───────────── ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Conflict SystemAdministration PermissionSet C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\permissionsets\SystemAdministration.permissionset-meta.xml
Error (1): There are changes in the org that conflict with the local changes you're trying to deploy.
Try this:
To overwrite the remote changes, rerun this command with the --ignore-conflicts flag. sf
To overwrite the local changes, run the "sf project retrieve start" command with the --ignore-conflicts flag.
With this feedback I'd found some issues created in the past, with similar cenario:
- https://github.com/forcedotcom/cli/issues/2293 and
- https://github.com/forcedotcom/cli/issues/2244.
And found this documents about conflict config to:
- https://developer.salesforce.com/tools/vscode/en/deploy-changes/detect-conflicts and
- https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_source_tracking_resolve_conflicts.htm
So that I'm changing the environment variable SF_DISABLE_SOURCE_MEMBER_POLLING=true to bypass this from my side, but in our CI/CD job I'll need to check how can we always change it, due to a new agent is created in every single commit that we push to our integration branches.
Additionally, we created the case with Salesforce support to evaluate it to, but I keep the doublt about why this conflict Error message are not affecting sandbox Non-Previews.
Hi @shetzel
We've got an update from Salesforce support side, and unfortunatelly they do not accepted the issue from Org side, the conclusion of my case:
Case Resolution Details:
As discussed over the meeting, first, we validated & found that the project structure including package.xml and procedure you are doing is correct.
Secondly, we tried to deploy the same files/package through the workbench & it was successful.
Conclusion: The issue seems with the vs code / extensions / workspace / compatibility etc. as we verified the issue is not with the org.
Thanks & Regards,
Am***ne
Developer Support Engineer
Working Hours: Mon-Fri | 08:00 AM to 05:00 PM EST
So that, I've changed SF_DISABLE_SOURCE_MEMBER_POLLING to true:
PS C:\Users\renan.***\Workspace\sforce-sfdc-***> sf config set SF_DISABLE_SOURCE_MEMBER_POLLING true --global
Did you mean org-metadata-rest-deploy? (y/N)
Set Config
========================================
| Name Value Success
| ──────────────────────── ───── ───────
| org-metadata-rest-deploy true true
Is this org-metadata-rest-deploy the right variable?
With this ENV variable configured the result was:
PS C:\Users\renan.***\Workspace\sforce-sfdc-***> sf project deploy start --target-org int --source-dir .\force-app\main\default\permissionsets\SystemAdministration.permissionset-meta.xml --test-level NoTestRun --dry-run -w 360 --verbose
Warning: Unable to find type ExperienceResource in registry
Warning: Unable to find type ExperienceResource in registry
Warning: Unable to find type ExperienceResource in registry
STATE FULL NAME TYPE FILE PATH
──────── ──────────────────── ───────────── ───────────────────────────────────────────────────────────────────────────────
Conflict SystemAdministration PermissionSet C:\Users\renan.***\Workspace\sforce-sfdc-***\force-app\main\default\permissionsets\SystemAdministration.permissionset-meta.xml
Error (1): There are changes in the org that conflict with the local changes you're trying to deploy.
Try this:
To overwrite the remote changes, rerun this command with the --ignore-conflicts flag. sf
To overwrite the local changes, run the "sf project retrieve start" command with the --ignore-conflicts flag.
C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\core\lib\errors\index.js:46
throw new exit_1.ExitError(code);
^
ExitError: EEXIT: 130
at Object.exit (C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\core\lib\errors\index.js:46:11)
at DeployMetadata.exit (C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@oclif\core\lib\command.js:180:16)
at process.<anonymous> (C:\Users\renan.***\node\node-v16.13.0-win-x64\node_modules\@salesforce\cli\node_modules\@salesforce\plugin-deploy-retrieve\node_modules\@salesforce\sf-plugins-core\lib\sfCommand.js:201:22)
at process.emit (node:events:402:35) {
code: 'EEXIT',
oclif: { exit: 130 },
suggestions: undefined
}
So that we added --ignore-conflicts
PS C:\Users\renan.***\Workspace\sforce-sfdc-***> sf project deploy start --target-org int --source-dir .\force-app\main\default\permissionsets\SystemAdministration.permissionset-meta.xml --test-level NoTestRun --dry-run -w 360 --ignore-conflicts --verbose
Warning: Unable to find type ExperienceResource in registry
Warning: Unable to find type ExperienceResource in registry
Warning: Unable to find type ExperienceResource in registry
...
With the non-preview sandbox, any change, the deploy command runs well, with or without the ENV variable set.
PS C:\Users\renan.***\Workspace\sforce-sfdc-***> sf project deploy start --target-org stage --source-dir .\force-app\main\default\permissionsets\SystemAdminlt\permissionsets\SystemAdministration.permissionset-meta.xml --test-level NoTestRun --dry-run -w 360 --verbose
Deploying (dry-run) v59.0 metadata to renan.***@***.stage using the v59.0 REST API.
Deploy ID: 0Af***0AL
Status: In Progress | ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ | 0/1 ComponentsWarning: Polling for 1 SourceMembers timed out after 1 attempts (last 0 were empty).
Validated Source
==============================================================================================================================
| State Name Type Path
| ─────── ──────────────────── ───────────── ──────────────────────────────────────────────────────────────────────────────
| Changed SystemAdministration PermissionSet force-app\main\default\permissionsets\SystemAdministration.permissionset-meta.xml
Dry-run complete.
Need to ask, when the source-track was change and impact the deploy command? I'm asking this due to a week before of the creation of this issue, we weren't being impacted for this conflicts.
Is this org-metadata-rest-deploy the right variable?
No. SF_DISABLE_SOURCE_MEMBER_POLLING is an environment variable, not a SF config variable so you can't set it with sf config set. You have to export SF_DISABLE_SOURCE_MEMBER_POLLING=true or the equivalent for your operating system. However, don't bother with setting this unless you don't care about source tracking data.
There appear to be several things going on:
- deploy is taking longer. That is primarily due to the Spring release rolling out (reduced compute resources for deployment), but also the communities code changed how source tracking works for ExperienceBundle and DigitalExperienceBundle metadata types (i.e., communities). This change is causing the
Warning: Unable to find type ExperienceResource in registrywarning, but that is not causing a problem. - You are running into source tracking conflicts when deploying. That's why adding the
--ignore-conflictsflag causes the deploy to succeed. However, you should know that what you deployed is different from what is in the org (that's why the conflict error is there). If you don't want to have source tracking enabled in that sandbox you can runsf org disable tracking -o <the_org>. That is your choice, and you will no longer see conflict warnings so you might overwrite changes made in that sandbox. The sf CLI enables source tracking by default with orgs that support it. This might be a change that you were not aware of. - That specific warning should not be displayed by the CLI. That is the only bug in this report for the CLI, and we can get an internal work item created to track it.
![git2gus[bot] avatar](https://avatars.githubusercontent.com/in/19654?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi @shetzel,
Understood about the source tracking, however we already have the source of trough in our git repo, so that the source tracking inside the sandbox seems to be unecessary, since we will allways deploy on the sandbox what is in our repository.
Additionlly, I've asked when the source tracking was an gate that triggers Warning and need to be configured to be ignored in our deployments, due to the fact that when we have enalbled DevHub and some dependencies an year ago, any Warning or Error with source tracking were noted or triggered since then, so I feel that the new Release in some way is making the conflicts evaluation mandatory from Org side, with or witouh --ignore-conflicts as I posted before.
From our side, We'll try to make some changes about config in our project and CI/CD steps (pipeline as code).
Best regards Thank you for the patience
Hello, @renanlq have you resolve your issue about "Error (1): There are changes in the org that conflict with the local changes you're trying to deploy." ?
I have the same issue since sfdx command to sf command change
Hello @nicolashamez-dev, here is something you might wanna try:
We where facing the same problems described here in our org when running sf project deploy start, and after analyzing the log generated by --dev-debug we suspected it might be because source tracking was enabled in our sandbox.
In short, we discovered you can disable source tracking locally, by running the following command in the sfdx project folder:
sf org disable tracking
After that the issue was gone.
Of course there is the possibility of disabling source tracking for sandboxes in the devhub org (Setup > Development > Dev Hub), and refresh the sandbox. That might disable it directly in the sandbox, but we didn't try that yet.
Here's the sf command reference link:
https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference_org_commands_unified.htm#cli_reference_org_disable_tracking_unified