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.

Sign up for GitHub

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

Jump to bottom

[FEATURE] refresh should optionally take journey keys to identify relevant triggeredSends #1891

Open
JoernBerkefeld opened this issue Nov 22, 2024 · 0 comments
Open

[FEATURE] refresh should optionally take journey keys to identify relevant triggeredSends #1891

JoernBerkefeld opened this issue Nov 22, 2024 · 0 comments
Labels
c/journey COMPONENT c/triggeredSend COMPONENT enhancement New feature or request; requires increasing the minor version of mcdev. Jira issue-type "Story"
Milestone
7.6.0 B

Comments

@JoernBerkefeld
Copy link
Contributor

often times, you will want to refresh only emails in a single journey. right now, that's difficult to do because the function only accepts triggered send keys.

potential implications for deploy --refresh have to be considered! I'm assuming this will only trigger for assets at the moment but it has to be double-checked
@JoernBerkefeld JoernBerkefeld added enhancement New feature or request; requires increasing the minor version of mcdev. Jira issue-type "Story" c/journey COMPONENT c/triggeredSend COMPONENT labels Nov 22, 2024
@JoernBerkefeld JoernBerkefeld added this to the 7.6.0 milestone Nov 22, 2024
@JoernBerkefeld JoernBerkefeld mentioned this issue Dec 6, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c/journey COMPONENT c/triggeredSend COMPONENT enhancement New feature or request; requires increasing the minor version of mcdev. Jira issue-type "Story"
Projects
None yet
Milestone
7.6.0 B
Development

No branches or pull requests
1 participant
@JoernBerkefeld