Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] publishing multiple SF-triggered journeys in parallel causes error #1627

Closed
2 tasks done
JoernBerkefeld opened this issue Aug 29, 2024 · 1 comment · Fixed by #1629 or #1635
Closed
2 tasks done

[BUG] publishing multiple SF-triggered journeys in parallel causes error #1627

JoernBerkefeld opened this issue Aug 29, 2024 · 1 comment · Fixed by #1629 or #1635
Assignees
Labels
bug Something isn't working c/journey COMPONENT
Milestone

Comments

@JoernBerkefeld
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

When trying to publish multiple SF-Data-Entry Event based journeys you get errors for all but one of them (in my test I tried activating 3 and only 1 got through.

Code: Salesforce_JB_Triggers_Error
Details: DUPLICATE_VALUE;The fullName: JBSystemFlow_CampaignMember-141 for Flow version is not unique.;;Flow Save failed. Unable to activate the Journey, the Sales Cloud user may not have correct permissions. Activating a Journey requires the Run Flow and Manage Force.com Flow permissions.

Expected Behavior

hitting the publish endpoint should be directly followed by hitting the status endpoint and only when that's done should we try to activate the next journey. at least for sf-journeys

Steps To Reproduce

14:52:31.800 info: :: publish journey on R1/SIT
14:52:32.358 info: Found 3 journey results
14:52:32.432 info: - queued for publishing journey: 69af4a4b-2e35-bca3-72b3-65a7fa2ecb72
14:52:32.493 info: - queued for publishing journey: 45c5315f-94c0-6dda-b390-a7c199cc548b
14:52:32.502 info: - queued for publishing journey: 99ef8ef8-976d-d9cf-2943-731c1a221d78
14:52:32.503 info: Checking status of 3 published items
14:52:37.922 info: - journey 69af4a4b-2e35-bca3-72b3-65a7fa2ecb72: publishing still in progress
14:52:40.339 info: - journey 69af4a4b-2e35-bca3-72b3-65a7fa2ecb72: publishing still in progress
14:52:42.723 info: - journey 69af4a4b-2e35-bca3-72b3-65a7fa2ecb72: publishing still in progress
14:52:45.115 info: - journey 69af4a4b-2e35-bca3-72b3-65a7fa2ecb72: publishing still in progress
14:52:47.507 info: - journey 69af4a4b-2e35-bca3-72b3-65a7fa2ecb72: publishing still in progress
14:52:49.909 info: - journey 69af4a4b-2e35-bca3-72b3-65a7fa2ecb72: publishing still in progress
14:52:52.345 error: - journey 69af4a4b-2e35-bca3-72b3-65a7fa2ecb72: publishing failed.
14:52:52.346 error: Errors:
14:52:52.346 error: #1
14:52:52.347 error: Code: Salesforce_JB_Triggers_Error
14:52:52.347 error: Details: DUPLICATE_VALUE;The fullName: JBSystemFlow_CampaignMember-141 for Flow version is not unique.;;Flow Save failed. Unable to activate the Journey, the Sales Cloud user may not have correct permissions. Activating a Journey requires the Run Flow and Manage Force.com Flow permissions.
14:52:52.347 error: Additional Info:
14:52:52.347 error: activityKey: TRIGGER
14:52:52.348 error: activityId: d50210fc-9979-491e-85f3-5187dcc9b153
14:52:52.348 error: activityType: SalesforceObjectTriggerV2
14:52:52.348 error: definitionId: 9c503515-2a6b-4e6c-80e7-ad69629b1904
14:52:52.349 error:
14:52:52.735 info: - journey 45c5315f-94c0-6dda-b390-a7c199cc548b: publishing still in progress
14:52:55.188 info: - journey 45c5315f-94c0-6dda-b390-a7c199cc548b: publishing still in progress
14:52:57.618 info: - journey 45c5315f-94c0-6dda-b390-a7c199cc548b: publishing still in progress
14:53:00.010 info: - journey 45c5315f-94c0-6dda-b390-a7c199cc548b: publishing still in progress
14:53:02.448 info: - journey 45c5315f-94c0-6dda-b390-a7c199cc548b: publishing still in progress
14:53:04.862 info: - journey 45c5315f-94c0-6dda-b390-a7c199cc548b: publishing still in progress
14:53:07.272 info: - journey 45c5315f-94c0-6dda-b390-a7c199cc548b: publishing succeeded
14:53:07.668 error: - journey 99ef8ef8-976d-d9cf-2943-731c1a221d78: publishing failed.
14:53:07.669 error: Errors:
14:53:07.669 error: #1
14:53:07.670 error: Code: Salesforce_JB_Triggers_Error
14:53:07.670 error: Details: DUPLICATE_VALUE;The fullName: JBSystemFlow_CampaignMember-141 for Flow version is not unique.;;Flow Save failed. Unable to activate the Journey, the Sales Cloud user may not have correct permissions. Activating a Journey requires the Run Flow and Manage Force.com Flow permissions.
14:53:07.671 error: Additional Info:
14:53:07.671 error: activityKey: TRIGGER
14:53:07.671 error: activityId: 9cf1e4d2-ce7e-4f6f-98f2-82082fd50fa2
14:53:07.672 error: activityType: SalesforceObjectTriggerV2
14:53:07.672 error: definitionId: 8d1712c4-d80b-40d2-a365-b1dde83de3fe
14:53:07.672 error:
14:53:07.673 info: Published 1 of 3 items
14:53:07.673 info: :: Done

Version

7.3.0

Environment

  • OS:
  • Node:
  • npm:

Participation

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

Additional comments

No response

Copy link

Closed by #1629.

@JoernBerkefeld JoernBerkefeld mentioned this issue Aug 30, 2024
11 tasks
JoernBerkefeld added a commit that referenced this issue Aug 30, 2024
#1627: run publish journey action sequentially for multi-step journey…
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working c/journey COMPONENT
Projects
None yet
1 participant