[BUG] salesforce triggered journeys cannot be published after deploy

[JoernBerkefeld]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

something is off in how we deploy things and while the API doesn't block this from happening, it later blocks the deploy.

Expected Behavior

idea:

check if fields are available on connected org.

journeybuilder itself executes this (with different internal endpoints but same / similar results):

1. {{restEndPoint_v2}}/data/v1/integration/member/salesforce/workflowobjects - that gives us ALL salesforce core objects from the connected org
2. {{restEndPoint_v2}}/data/v1/integration/member/salesforce/object/{{objectName}}/referenceobjects - that gives us a list of other objects we need to query because they are related using the objectName from eventDefinition.configurationArguments.objectAPIName or journey.triggers[0].configurationArguments.objectAPIName
3. {{restEndPoint_v2}}/legacy/v1/beta/integration/member/salesforce/object/{{objectName}}/ - this takes [].referenceObjectName from call 2 for as many times as there are relationships found in (2) and gets the full field list. JB does this nicer with a single API call but I cant figure out how to work the published ones for that.

Steps To Reproduce

1. Go to '...'
2. Click on '....'
3. Run '...'
4. See error...

Version

7.1.4

Environment

• OS:
• Node:
• npm:

Participation

• I am willing to submit a pull request for this issue.

Additional comments

No response

[github-actions]

Closed by #1604.