Skip to main content
luizb1735
April 12, 2024
Question

Deployment

  • April 12, 2024
  • 12 replies
  • 1 view

I need to send my code that is in the test environment to the production environment, however, there are some group identifier errors. I do not make sense.

Can someone help?

Begin transport.
2024-04-12 14:29:41.99 DEBUG group 61 20a13bee-28e1-4b24-a02e-21ee270d3116 Loop detected: [group:61, group:160]
2024-04-12 14:29:41.99 DEBUG group 61 Breaking loop [group:61, group:160]. group:160 will be transported with its reference to 61 nulled out and will require a second pass.

12 replies

karumurua531442
April 12, 2024

Hi [mention:ec860b9e5a494ba3b957398cdd9d291d:e9ed411860ed4f2ba0265705b8793d05]  we need more context on this , how are trying to send your code from test to prod env , which object deployment is throwing this error

luizb1735
luizb1735Author
April 12, 2024

PROD is empty, this is the first DEPLOY.

I'm trying to send the code COMPARE AND DEPLOY, it doesnt find any error on inspection, but when I deploy it fail. Do not show where is the problem.

mikes0011
Brainy
April 12, 2024

What do you get when you run Missing Precedents Checker?  I'm assuming by the above issue that it won't come up empty for you if you run it.  That would be the first clue.

The Expression Guru
harshk1671
April 12, 2024

Looks like child parent relationship between group 61 and group 160. As suggested in other answers already go for two deployments.
Or you can create a package with all the independent groups (Groups which does not have child groups) and deploy that first and then try for rest in the second deployment.