How to avoid logging an error when aborting a pipeline
up vote
8
down vote
favorite
By default an error is logged when I abort a pipeline in Sitecore XC9.
For example;
context.Abort("Abort pipeline", context);
Sometimes I want to abort a pipeline without logging an error, i.e. when it's valid to preempt the execution of the pipeline.
How to do this?
sitecore-commerce pipelines
edited Nov 28 at 18:22
Mark Cassidy♦
16.6k43180
asked Nov 28 at 7:36
Joost
63412
add a comment |
up vote
8
down vote
favorite
By default an error is logged when I abort a pipeline in Sitecore XC9.
For example;
context.Abort("Abort pipeline", context);
Sometimes I want to abort a pipeline without logging an error, i.e. when it's valid to preempt the execution of the pipeline.
How to do this?
sitecore-commerce pipelines
edited Nov 28 at 18:22
Mark Cassidy♦
16.6k43180
asked Nov 28 at 7:36
Joost
63412
1
@Dan Sinclair why did you remove the sitecore-commerce tag?
– Joost
Nov 28 at 13:46
Because this is not a commerce-specific question/solution. This appears to apply to any pipeline abort command; is that right?
– Dan Sinclair
Nov 28 at 14:26
1
No this is for XC only
– Mark Cassidy♦
Nov 28 at 15:55
add a comment |
up vote
8
down vote
favorite
up vote
8
down vote
favorite
By default an error is logged when I abort a pipeline in Sitecore XC9.
For example;
context.Abort("Abort pipeline", context);
Sometimes I want to abort a pipeline without logging an error, i.e. when it's valid to preempt the execution of the pipeline.
How to do this?
sitecore-commerce pipelines
edited Nov 28 at 18:22
Mark Cassidy♦
16.6k43180
asked Nov 28 at 7:36
Joost
63412
By default an error is logged when I abort a pipeline in Sitecore XC9.
For example;
context.Abort("Abort pipeline", context);
Sometimes I want to abort a pipeline without logging an error, i.e. when it's valid to preempt the execution of the pipeline.
How to do this?
sitecore-commerce pipelines
sitecore-commerce pipelines
edited Nov 28 at 18:22
Mark Cassidy♦
16.6k43180
asked Nov 28 at 7:36
Joost
63412
edited Nov 28 at 18:22
Mark Cassidy♦
16.6k43180
asked Nov 28 at 7:36
Joost
63412
edited Nov 28 at 18:22
Mark Cassidy♦
16.6k43180
edited Nov 28 at 18:22
Mark Cassidy♦
16.6k43180
edited Nov 28 at 18:22
Mark Cassidy♦
16.6k43180
16.6k43180
asked Nov 28 at 7:36
Joost
63412
asked Nov 28 at 7:36
Joost
63412
asked Nov 28 at 7:36
Joost
63412
63412
1
@Dan Sinclair why did you remove the sitecore-commerce tag?
– Joost
Nov 28 at 13:46
Because this is not a commerce-specific question/solution. This appears to apply to any pipeline abort command; is that right?
– Dan Sinclair
Nov 28 at 14:26
1
No this is for XC only
– Mark Cassidy♦
Nov 28 at 15:55
add a comment |
1
@Dan Sinclair why did you remove the sitecore-commerce tag?
– Joost
Nov 28 at 13:46
Because this is not a commerce-specific question/solution. This appears to apply to any pipeline abort command; is that right?
– Dan Sinclair
Nov 28 at 14:26
1
No this is for XC only
– Mark Cassidy♦
Nov 28 at 15:55
1
1
@Dan Sinclair why did you remove the sitecore-commerce tag?
– Joost
Nov 28 at 13:46
@Dan Sinclair why did you remove the sitecore-commerce tag?
– Joost
Nov 28 at 13:46
Because this is not a commerce-specific question/solution. This appears to apply to any pipeline abort command; is that right?
– Dan Sinclair
Nov 28 at 14:26
Because this is not a commerce-specific question/solution. This appears to apply to any pipeline abort command; is that right?
– Dan Sinclair
Nov 28 at 14:26
1
1
No this is for XC only
– Mark Cassidy♦
Nov 28 at 15:55
No this is for XC only
– Mark Cassidy♦
Nov 28 at 15:55
add a comment |
1 Answer
1
active
oldest
votes
up vote
17
down vote
accepted
Add a magic "Ok|" string to the abort message, e.g:
context.Abort("Ok|Abort pipeline", context);
It turns out that the implementation of Abort checks for the magic "Ok|" string:
public override void Abort(string message, object context)
{
base.Abort(message, context);
if (message.Contains("Ok|"))
return;
this.Logger.LogError(string.Format("PipelineAbort:{0}", (object) message), Array.Empty());
}
answered Nov 28 at 7:36
Joost
63412
1
wow, nice catch
– Vlad Iobagiu
Nov 28 at 7:45
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "664"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f15205%2fhow-to-avoid-logging-an-error-when-aborting-a-pipeline%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
17
down vote
accepted
Add a magic "Ok|" string to the abort message, e.g:
context.Abort("Ok|Abort pipeline", context);
It turns out that the implementation of Abort checks for the magic "Ok|" string:
public override void Abort(string message, object context)
{
base.Abort(message, context);
if (message.Contains("Ok|"))
return;
this.Logger.LogError(string.Format("PipelineAbort:{0}", (object) message), Array.Empty());
}
answered Nov 28 at 7:36
Joost
63412
1
wow, nice catch
– Vlad Iobagiu
Nov 28 at 7:45
add a comment |
up vote
17
down vote
accepted
Add a magic "Ok|" string to the abort message, e.g:
context.Abort("Ok|Abort pipeline", context);
It turns out that the implementation of Abort checks for the magic "Ok|" string:
public override void Abort(string message, object context)
{
base.Abort(message, context);
if (message.Contains("Ok|"))
return;
this.Logger.LogError(string.Format("PipelineAbort:{0}", (object) message), Array.Empty());
}
answered Nov 28 at 7:36
Joost
63412
1
wow, nice catch
– Vlad Iobagiu
Nov 28 at 7:45
add a comment |
up vote
17
down vote
accepted
up vote
17
down vote
accepted
Add a magic "Ok|" string to the abort message, e.g:
context.Abort("Ok|Abort pipeline", context);
It turns out that the implementation of Abort checks for the magic "Ok|" string:
public override void Abort(string message, object context)
{
base.Abort(message, context);
if (message.Contains("Ok|"))
return;
this.Logger.LogError(string.Format("PipelineAbort:{0}", (object) message), Array.Empty());
}
answered Nov 28 at 7:36
Joost
63412
Add a magic "Ok|" string to the abort message, e.g:
context.Abort("Ok|Abort pipeline", context);
It turns out that the implementation of Abort checks for the magic "Ok|" string:
public override void Abort(string message, object context)
{
base.Abort(message, context);
if (message.Contains("Ok|"))
return;
this.Logger.LogError(string.Format("PipelineAbort:{0}", (object) message), Array.Empty());
}
answered Nov 28 at 7:36
Joost
63412
answered Nov 28 at 7:36
Joost
63412
answered Nov 28 at 7:36
Joost
63412
answered Nov 28 at 7:36
Joost
63412
63412
1
wow, nice catch
– Vlad Iobagiu
Nov 28 at 7:45
add a comment |
1
wow, nice catch
– Vlad Iobagiu
Nov 28 at 7:45
1
1
wow, nice catch
– Vlad Iobagiu
Nov 28 at 7:45
wow, nice catch
– Vlad Iobagiu
Nov 28 at 7:45
add a comment |
Thanks for contributing an answer to Sitecore Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f15205%2fhow-to-avoid-logging-an-error-when-aborting-a-pipeline%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
@Dan Sinclair why did you remove the sitecore-commerce tag?
– Joost
Nov 28 at 13:46
Because this is not a commerce-specific question/solution. This appears to apply to any pipeline abort command; is that right?
– Dan Sinclair
Nov 28 at 14:26
1
No this is for XC only
– Mark Cassidy♦
Nov 28 at 15:55