How to avoid logging an error when aborting a pipeline











up vote
8
down vote

favorite
2












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







share|improve this question




















  • 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















up vote
8
down vote

favorite
2












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







share|improve this question




















  • 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













up vote
8
down vote

favorite
2









up vote
8
down vote

favorite
2






2





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







share|improve this question















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 28 at 18:22









Mark Cassidy♦

16.4k43179




16.4k43179










asked Nov 28 at 7:36









Joost

58211




58211








  • 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




    @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










1 Answer
1






active

oldest

votes

















up vote
16
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());

}





share|improve this answer

















  • 1




    wow, nice catch
    – Vlad Iobagiu
    Nov 28 at 7:45











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
});


}
});














draft saved

draft discarded


















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
16
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());

}





share|improve this answer

















  • 1




    wow, nice catch
    – Vlad Iobagiu
    Nov 28 at 7:45















up vote
16
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());

}





share|improve this answer

















  • 1




    wow, nice catch
    – Vlad Iobagiu
    Nov 28 at 7:45













up vote
16
down vote



accepted







up vote
16
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());

}





share|improve this answer












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());

}






share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 28 at 7:36









Joost

58211




58211








  • 1




    wow, nice catch
    – Vlad Iobagiu
    Nov 28 at 7:45














  • 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


















draft saved

draft discarded




















































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.




draft saved


draft discarded














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





















































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







-

Popular posts from this blog

AnyDesk - Fatal Program Failure

Image
up vote 0 down vote favorite Good day all. I have a window that pops up saying Fatal Program Failure (AnyDesk). This is what I have done so far: Uninstalled AnyDesk and reinstalled it. ( The window still appeared ) I disabled AnyDesk start up in Msconfig and the window seems to have disapeared. Lastly I made sure that AnyDesk worked by remoting into it, and it worked. Today the same window appeared. How do I get rid of this window? remote-desktop share | improve this question edited 10 hours ago Tomasz Jakub Rup 552 3 13 ...
Read more

How to calibrate 16:9 built-in touch-screen to a 4:3 resolution?

Image
up vote 0 down vote favorite I need help with an issue we're facing in a project where we are moving from a Windows-based POS environment to one running on CentOS7. The problem consists of a number of factors, please find the details below: The supplier of our POS application will only deliver an application that is hard-coded to run in a 1024:768 4:3 format. The hardware we are using is a POS unit from HP that has a built-in 16:9 touch-screen. The employees using this solution is not supposed to see nor have access to anything but the POS application. Our sales organization demands that touch is an available feature when going live with the new POS environment. Going further into this, allow me to explain what we have encountered on the way trying to achieve the goal of having a touch-screen: We've simply change...
Read more

QoS: MAC-Priority for clients behind a repeater

Image
1 1 I've setup a wireless network using a Linksys-Router (DD-WRT) as an AP and a TP-Link repeater for range extension. To manage bandwith for specific users, I've setup QoS-Rules on the AP (DD-WRT) using MAC-Priority: However the AP shows only the Repeater's MAC and the MACs of users inside the AP-Range. The MAC addresses of users behind the Repeater are not listed : The purple MAC is not listed in the AP-Clientlist. Its related to a device connected via the TP-Link repeater. Q: How can I setup MAC-Priority for repeater-clients? Do I simply add the purple MAC in AP-MAC priority list although it's not listed as a client? I want to setup specific priority instead of giving one priority for all clients behind the repeater by adding the repeater's MAC in the MAC priority list in the AP as ...
Read more