DevOps Center エラー関係のまとめ

+ [DevOps Center まとめに戻る](https://qiita.com/Keiji_otsubo/items/3969e9a6c09cf727a4d9)

+ [DevOps Center のインストールエラー](https://qiita.com/Keiji_otsubo/items/5cf7b820ebb6d5bb4f11)

+ [Response code 403 (Forbidden) : DevOps Center](https://qiita.com/Keiji_otsubo/items/e3b8e23f19cbc0f26d2a)
+ [【未解決】Salesforce DevOps Center で変更を手動でプルしている間、すべてのカスタム フィールドが表示されない](https://trailhead.salesforce.com/en/trailblazer-community/feed/0D54S00000Jze1XSAR)
+ [UAT environment 受け入れ環境とDevOps Center](https://qiita.com/Keiji_otsubo/items/6ae2aec83034693c7a5b)
+ [Unable to see deleted custom field in work item](https://trailhead.salesforce.com/en/trailblazer-community/feed/0D54S00000IQPeiSAH)
+ [DevOps Center リリース環境をプロジェクトに接続できません](https://qiita.com/Keiji_otsubo/items/f04130b79bcf12e0a5ac)
+ [DevOps Center : Promotion Blocked](https://qiita.com/Keiji_otsubo/items/062605b8b69117a81626)
+ [How to get DevOps enabled in Sandbox](https://trailhead.salesforce.com/en/trailblazer-community/feed/0D54S00000JdUQU)

DevOps Center has not been enabled for your org.
Ask a Salesforce admin to enable it in Setup > Development > DevOps Center.

+ [カスタム メタデータのインポート時に変更を検出する方法は?](https://trailhead.salesforce.com/en/trailblazer-community/feed/0D54S00000Jdr11)

そのツールがバックエンドで変更セットを使用してこれらのメタデータ タイプを組織にロードしている場合、それも問題を引き起こす可能性があります。

+ [DevOps Center のプル リクエストに完全なセキュリティ プロファイル XML が含まれていない](https://trailhead.salesforce.com/en/trailblazer-community/feed/0D54S00000Jy8zl)

DevOps Center を使用してプロファイルを管理したくない場合は、.forceignore ファイルを使用してプロファイルがコミットおよび展開されないようにすることができます。最後に、プロファイルと権限に関する Salesforce の一般的な方向性は、プロファイルよりも権限セットを使用することです。  

+ [Getting sf_devops:Too many callouts: 101 exception](https://qiita.com/Keiji_otsubo/items/f8ef6602c62221a9d10f)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/30778751-dfe9-4d30-f084-253a3cec5e97.png)


+ [DevOps Center エラーまとめ: There was internal data model　error](https://qiita.com/Keiji_otsubo/items/1f5bf1d34bffdb5f7794)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/009a4dd0-c36b-ce1a-45d3-e02ce3fd92ff.png)

+ [There was an error. Please reload the page or contact your system administrator if the problem persists.](https://qiita.com/Keiji_otsubo/items/1bb8afd2d9cd3ce0bf94)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/1ff33624-9391-87ec-60d3-e33904838a0b.png)


+ [One of our devs is stuck with "Background Sync in Progress" and "Collaboration error".](https://trailhead.salesforce.com/en/trailblazer-community/feed/0D54S00000JdZGW)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/c63b0526-e41b-f7a2-71f3-49c5364004ea.png)

あなた/あなたの組織管理者は、組織に共同作業者を追加するために、[ここで説明されている手順](https://docs.github.com/en/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)に従うことができます。
これらの手順に従って、コラボレーターを 1 つの組織リポジトリにのみ追加することもできます。

+ [作業項目が「クローン リポジトリ」ステージでスタックしており、Devops Center で何もできなくなりました。](https://trailhead.salesforce.com/en/trailblazer-community/feed/0D54S00000Jdnzn)

本質的に「立ち往生」しているプロモーションがある場合。その後、最大約 2 時間後にタイムアウトするはずです。この時間が経過してもプロモーションが自動的に修正されないことがわかった場合は、Lightning Experience ビューに移動して、ステータスが「進行中」のままになっている Async_Operation_Result__c レコードを見つけることができるはずです。このステータスを「エラー」に変更すると、プロモーションを再試行できるようになります。 

+ [How to re-authorize Github oauth App?](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000NHLlx)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/34f686b0-e053-1c7b-04ab-0ed7b25fbc54.png)


:::note
Please try Mike Olson's steps, described in this thread, to re-initiate the authentication in to GitHub:

https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000HEPCASA5
:::

:::note
My company just enabled SSO for my Github Org overnight so was getting the same error running git pull. I fixed this with the following steps.

Open Credential Manager in Windows and delete the existing credential for github.com
Re-initialise the cred manager in git bash: git config --global credential.helper manager-core
Re-run git pull and follow the pop-up instructions to authenticate in a browser (which happened automatically for me with SSO).
:::


+ [This work item was merged outside of DevOps Center and must be promoted.](https://trailhead.salesforce.com/en/trailblazer-community/feed/0D54S00000JdmNi)
それは非常に奇妙です。これは、DevOps Center が GitHub から実際には発生しなかったイベントを受け取ったことを意味するためです。解決するために私たちができる最善の方法は、PR を手動でマージする (つまり、作業項目を昇格させたい場合) か、PR を閉じる (必要に応じて DevOps センターが新しいものを開く原因となる) ことだと思います。 



+ [There was an error. Please reload the page](https://qiita.com/Keiji_otsubo/items/bd4d99d91f3ccc65e90e)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/27ed809d-7805-8b33-90da-eb8d2610c431.png)


+ [作業項目 - ブロックされたレビューの作成](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000Jfa4c)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/eb5ac9c7-fc35-d6e7-c74f-6b23b37a15f5.png)

DOCをv5.3.0にアップグレードした後、問題が発生しなかったことをお知らせしたいと思います。

+ [類似:2023/01/18解決](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000NQ423)

Between Beta and GA, we updated DevOps Center to use a newer version of the SFDX source-deploy-retrieve library, and it's certainly possible that there is a bug/regression there. Could I trouble one of you experiencing this issue to try performing a force:source:deploy from the SF CLI for the layout with a parenthesis in its name, to see if it is successful or if it fails in the same way?

Beta と GA の間に、SFDX source-deploy-retrieve ライブラリの新しいバージョンを使用するように DevOps Center を更新しましたが、そこにバグ/リグレッションがある可能性は確かにあります。この問題が発生している方の 1 人に、SF CLI から force:source:deploy を名前に括弧が含まれるレイアウトに対して実行してみて、それが成功するか、同じように失敗するかを確認していただけますか?

I've tried the force:source:deploy on one of the layouts and it works without any issues:
![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/7c60275e-b652-a60f-7ea7-d029a5d24f62.png)
It looks like DevOps is having troubles recognizing the changed metadata between source(workitem) and destination(uat in our scenario) branches in GitHub repo if there is a parentheses in name, and doesn't include such metadata items in deployment.
名前に括弧があり、デプロイメントにそのようなメタデータ項目が含まれていない場合、DevOps は GitHub リポジトリのソース (workitem) と宛先 (このシナリオでは uat) ブランチの間で変更されたメタデータを認識するのに問題があるようです。

Also if I select deployment option 'All Metadata' then everything is getting deployed with no issues.
また、展開オプション「すべてのメタデータ」を選択すると、すべてが問題なく展開されます。

# Required field are missing

+ [Error with Swapping Environments](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000Jfl2e)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/ccfc6394-8185-90e4-cc06-c81859ebc430.png)

:::note
The error "Required field are missing" when swapping environments in Salesforce can be caused by a number of factors. Here are a few things you can check to troubleshoot this issue:

1. Check the required fields: Make sure that all required fields in the source and target environments have been filled out correctly. Required fields must contain a value in order to complete the swap process.
2. Check the Dev Hub org: Make sure that the Dev Hub org in your Salesforce organization is correctly set up and has the necessary permissions.
3. Check the Dev Ops settings: Make sure that Dev Ops has been enabled in both the source and target environments, and that all necessary settings have been configured correctly.
4. Check for errors in the Dev Hub org: If you are using the Dev Hub org to perform the swap, check for any errors in the Dev Hub org that may be preventing the swap from completing.
5.Check for errors in the source and target environments: Check for any errors in the source and target environments that may be causing the swap to fail.

I hope these suggestions help you resolve the error you are seeing when swapping environments in Salesforce. If you are still having trouble after trying these steps, you may want to consider reaching out to Salesforce Support for further assistance.
:::



# Case-Case Layout %28Admin View%29 of Type Layout failed to deploy due to Invalid field:SOLUTION.ISSUE in related list:RelatedSolutionList

+ [Environment sync fails](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S000000GG5ISAW)
+ [同じエラー](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000JftGx)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/163a9ba6-d0dc-b862-41e8-75a171624ef5.png)


:::note
This post suggests the error can still occur when including Aura metadata in the same deployment package

https://salesforce.stackexchange.com/questions/366476/invalid-fieldsolution-issue-in-related-listrelatedsolutionlist-when-deploying/366508#366508
:::

# Pipeline Unique Names

+ [Pipeline Unique Names](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000JgBEx)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/970ecd08-bc72-6aa4-09e3-1732cd67f000.png)

:::note
I ended up finding the solution. If you go to the projects app and changed the name there all is well. Trying to change it in DevOps Center doesn’t work.
:::

# CREATE REVIEW is greyed out

+ [CREATE REVIEW is greyed out](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000JgDLJSA3)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/b3f085ba-dad0-a48b-44e6-8bcdb3fb3948.png)

:::note
Oh for heaven's sake. There is a required field at the bottom for comments. That was blank. As soon as I typed NA - the process moved.
:::

# Proxy object could not be cloned

+ [Error "Proxy object could not be cloned" when opening DevOps Center in Firefox](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000JgYfF)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/bea77794-b540-8a69-a4ee-09e0c8e450b8.png)


# プロモートされていないワークアイテムにメタデータが表示されない

私は最近、レコード タイプのメタデータを含む一部のワーク アイテムがターゲット組織に正しく展開されていないことに最近気付きました。リポジトリ レベルではすべて問題ないように見え、昇格が実行されると正しく実行されますが、組織をチェックインすると、レコード タイプに加えられた変更が展開されませんでした。このような状況を回避するためにできることはありますか?

+ [Metadata not displayed in unpromoted work items & Problems deploying 2 fields with the same API name from different objects](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000JgWp1)

# Rebase Completed Error

+ [Promoted WorkItem shows "Rebased Completed" error after promotion ends](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000JgZdZSAV)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/8000f112-710b-be16-acc7-20aba029376e.png)

:::note
It looks like there is a conflict when DevOps Center tries to rebase WI-000183 branch with staging branch that you'll have to fix manually in GitHub.

Something I'd do, using command line, to check what's going on is:

1. Clone the repository on your computer if you haven't done it already.
2. Then do a "git checkout staging" to move to the branch and most importantly download it branch locally.
3. Then do "git checkout WI-000183" to download the work item branch and change to it.
4. Then you can do "git rebase staging".
5. If there is a conflict happening, it will show there, then you can fix it.
6. When the conflict is fixed you can do "git add ." to add all the files that were conflicting.
7. And after that you can do "git rebase --continue" to make sure git knows the rebase has finished.
8. And last thing, do "git push origin WI-000183" to make sure the conflict is solved in GitHub.

After this, I think DevOps Center should realise you have committed new changes there, and let you go on. I have not find this scenario before, but it's possible this is what's going on.

Unfortunately I don't think we can do that from GitHub UI.
:::

# View Details for more information on the error. If the error is due to a dependency, re-try the sync and select the All option in Synchronization Options.

+ [Errors on Sync to next stage in pipeline](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000JggMo)

:::note
After doing a git pull from git command line, I did find the NamedCredential was changed by one of the Work Items.  I am trying to trace this through to see what happened from the git command line, because the UI doesn't give enough information.

git コマンド ラインから git pull を実行した後、NamedCredential が作業項目の 1 つによって変更されていることがわかりました。 UI では十分な情報が得られないため、git コマンド ラインから何が起こったのかを確認するために、これを追跡しようとしています。
:::

# Unable to create new projects in Organization Repo only Personal

+ [Unable to create new projects in Organization Repo only Personal](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000JghNL)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/711e7284-048e-aaeb-40d0-5a3f07f919fc.png)

:::note
I humbly submit my own solution. 
For the Repository "owner" I had been using my own (personal) Username and got only the repo created in my personal account. 

To get it created correctly in my org the trick is to use the org "name" not the org's account owner name. 
:::



# WI のステータス エラー、プロモーションのブロック。

+ [Status error on a WI, blocking promotion.](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000Osir8)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/a39fc6ce-ed16-f36f-d115-5b78ce44ea66.png)

# Unable to link Namespace Registry

+ [Unable to link Namespace Registry](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000FTMTv)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/3e324e64-e773-7fec-13c7-5f45ebcb58e8.png)

:::note
he DevHub Org and Dev org must be separate. I was entering devHub credentials in the pop up which was causing the issue. I created dev org and moved my work there and entered that org's credentials in Link Namespace Registry popup and it worked.
The settings mentioned in the article needs to be done in the DevHub org.

DevHub 組織と Dev 組織は分離する必要があります。ポップアップに devHub 資格情報を入力していたため、問題が発生していました。私は開発組織を作成し、そこに作業を移動し、その組織の資格情報を Link Namespace Registry ポップアップに入力したところ、機能しました。

この記事に記載されている設定は、DevHub 組織で行う必要があります。
:::

# Source Control System Sync error

+ [Source Control System Sync error](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000Pj2RT)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/0b8a4b49-023f-3d76-9fdb-7ce92a9f9aca.png)

:::note
I did end up clearing my cache yesterday and a few of the random issues that were blocking me from creating reviews on work items did seem to get cleared up. I am not seeing this error in the afternoon whereas in the morning it was all the time.

昨日、最終的にキャッシュをクリアし、作業項目のレビューの作成を妨げていたいくつかのランダムな問題が解消されたように見えました。午後にはこのエラーは表示されませんが、午前中は常に表示されていました。
:::

# Select An Org The link you were trying to access requires an Org to be selected. Please select the appropriate Org to access the desired page. Learn more here.

+ [Submit Support Case](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000PkgTp)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/f165bacc-c9c5-6e24-a37e-9189bcb8af0f.png)

:::note
Please follow this link- https://salesforce.stackexchange.com/questions/241833/unable-to-raise-a-case-to-salesforce-support

says, 
You cannot raise a case from any non-production org, including Developer Edition, Sandboxes, and Scratch Orgs. You will need to log in to your production org and raise a case there. If you have a problem with a specific Sandbox, include the Org Id in your case (there's a field for this purpose), and make sure you Grant Login Access to the Sandbox if necessary.

https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000A8OmWSAV
:::

# Admin of Type Profile failed to deploy due to cannot delete profile

+ [Admin of Type Profile failed to deploy due to cannot delete profile](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000NH6FA)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/e5f00e7b-3618-c660-2193-b5b391755e54.png)

:::note
Have you seen this doc topic: https://help.salesforce.com/s/articleView?id=sf.devops_center_setup_forceignore.htm

If you made a change to .forceignore after you activated the pipeline, then you have to manually make the updates in each branch. And then sometimes there's a delay between making the changes in GitHub and those changes being reflected in DevOps Center.

パイプラインをアクティブ化した後に .forceignore に変更を加えた場合は、各ブランチで手動で更新を行う必要があります。また、GitHub で変更を加えてから、その変更が DevOps Center に反映されるまでに遅延が発生する場合があります。
:::

# Element {http://soap.sforce.com/2006/04/metadata}nameSegment invalid at this location in type FlowActionCall

+ [Element {http://soap.sforce.com/2006/04/metadata}nameSegment invalid at this location in type FlowActionCall](https://qiita.com/Keiji_otsubo/items/35f76b077b976c73f692)

# Please reload the page or contact your system administrator

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/372bcc7b-151e-4a99-caeb-7b16cf0c7803.png)

+ [Error Message - Please reload the page or contact your system administrator if the problem persists.](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000QMteJ)

:::note
The root of the error is STORAGE_LIMIT_EXCEEDED.

 Please check this post: https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000HEh74SAD
:::

# 追加できない？

+ [Why not be able to add Dev Org?](https://trailhead.salesforce.com/trailblazer-community/feed/0D54V000074q2tZ)

:::note
you've assigned the user all of the appropriate DevOps Center permission sets, as per the setup instructions?

https://help.salesforce.com/s/articleView?id=sf.devops_center_assign_permsets.htm&type=5
:::

# Promotion Stopped Due to New Events

+ ["Promotion Stopped Due to New Events"](https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007HKxOASA1)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/946007b2-56e5-842b-5e8e-439c9802f72a.png)


:::note
That's actually a new feature that makes sure that DevOps Center has received all the events from GitHub so you don't find yourself in an undesirable state. It's not an error message but rather communication to wait a few more minutes so that your promotion is successful. 

これは実際には、DevOps Center が GitHub からすべてのイベントを受信して​​いることを確認して、望ましくない状態に陥らないようにする新機能です。これはエラー メッセージではなく、プロモーションが成功するまでさらに数分待つようにというメッセージです。 
:::

# This environment is already defined

+ [Can't add environment already defined](https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007KFsfz)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/98052293-77b2-88c4-cc1d-f93c9a1b2dfe.png)

:::note
The error message "This environment is already defined" in a DevOps Center likely means that you're trying to create an environment with a name that already exists in the system.

To resolve this error, you can try the following steps:

1. Change the environment name: Choose a different name for the environment that you're trying to create. This should ensure that the environment name is unique and doesn't conflict with any existing environments.
2. Delete the existing environment: If you're sure that the environment that you're trying to create is the same as an existing environment, you can try deleting the existing environment first. This will free up the environment name so that you can use it for your new environment. However, make sure to double-check that deleting the existing environment won't cause any issues with your DevOps process.
3. Contact DevOps support: If none of these solutions work, it's possible that there's a deeper issue with the DevOps Center that's causing the error message. In this case, you may need to contact your DevOps support team for further assistance. They can help you diagnose the issue and find a solution that works for your specific DevOps environment.


https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000O6TJPSA3
:::

# DevOps Center にはエラーの詳細が表示されませんか?

+ [DevOps Center not showing error details?](https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007T5E8h)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/f3116907-9a5d-9c65-8126-1e0a3089fd70.png)

:::note
これを投稿した後、午後中ずっと試していましたが、エラーの詳細はありませんでした。現時点で同期を試みたところです...成功しました! 
:::

# 実際のデプロイメントを行わずにマージする

+ [Merge without actual Deployment](https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007TuJLP)

、機能すると思われるプロセスを見つけました。シードしたいコンポーネントを抽出し、GitHub 内のブランチに直接コミットしています。非常に手動ですが、うまく機能しているようです。

# Entity of type 'CustomField' name xxxxxxxxxxx cannot be found

+ [Having an issue commiting in Dev OPs](https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007UsDSV)

:::note
We've run into this issue before and the only way we found to resolve it was to manually create the fields in the target org, then promote the work item that contains the delete changes for each field, which will delete the fields we just manually created.  Very inefficient, but haven't found another way to do this yet.

私たちは以前にこの問題に遭遇したことがあり、それを解決する唯一の方法は、ターゲット組織にフィールドを手動で作成し、各フィールドの削除変更を含む作業項目を昇格させることでした。これにより、フィールドが削除されます。手動で作成しただけです。非常に非効率ですが、これを行う別の方法はまだ見つかりません。
:::


# Rebase error 

+ [Rebase error while promoting work items to next stage](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000G2R14)

:::note
Rebase errors, in general, are related with dependencies between work items, and get resolved by promoting others first, or by using our Combine functionality.

一般に、リベース エラーは作業項目間の依存関係に関連しており、最初に他の作業項目を昇格するか、結合機能を使用することで解決されます。
:::

# There was an error. Please reload the page or contact your system administrator if the problem persists

+ [Add custom fields manually to work item error message](https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007UtVRw)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/42afb374-3145-5fb6-b3fb-68fb05892ebb.png)

:::note
It's has been reported as a known issue:

https://issues.salesforce.com/issue/a028c00000ix5Th/error-occurring-in-salesforce-devops-center-while-adding-the-component-type-as-custom-field-manually 
:::


# DevOp センターが次の環境に昇格できない (FSC)

+ [DevOp Center Fail to promote to next environment (FSC)](https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007XIceR)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/7be5d589-c92d-f273-2c8b-c7a502a082e0.png)

:::note
Got the same error

looks like you have managed the package on org with report type in next stage.  My workaround was to remove that report-type or manually check only the required Meata Data types. Exclude those report types. You will have to add those fields to the report type manually.

同じエラーが発生しました

次の段階でレポートタイプを使用して組織上のパッケージを管理しているようです。私の回避策は、そのレポート タイプを削除するか、必要な Meata データ タイプのみを手動でチェックすることでした。これらのレポート タイプを除外します。これらのフィールドをレポート タイプに手動で追加する必要があります。
:::

# Methods defined as TestMethod do not support Web service callouts

+ ['Methods defined as TestMethod do not support Web service callouts' Error](https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007UvGnb)

:::note
I also experienced this error message. In my case, I was running a test class for a particular class that was calling a method from another class, within which a callout was being made. This is why I was encountering this error.

私もこのエラーメッセージに遭遇しました。私の場合、別のクラスからメソッドを呼び出す特定のクラスのテスト クラスを実行しており、その中でコールアウトが行われていました。これが、このエラーが発生した理由です。
:::

# The Repeater screen component isn’t supported in this API version. To retrieve or deploy this flow, use API version 60.0 or later

+ [DevOps Promotion Failing: API Versions & Repeater Screen Flow Components](https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007er9h6)

:::note
I had to use change sets to push my new flow version to production and it worked just fine. Hopefully Salesforce can get this bug worked out soon!

新しいフロー バージョンを本番環境にプッシュするには変更セットを使用する必要がありましたが、問題なく動作しました。Salesforce がこのバグをすぐに解決してくれることを願っています。
:::

# Error connecting to Github

+ [We can’t log you in because of an authentication error. For help, contact your Salesforce administrator.](https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007ifrql)

:::note
This can help to reset authentications: 

https://help.salesforce.com/s/articleView?id=sf.devops_center_connect_diff_github_acct.htm&type=5 
:::