Will having excessive trigger campaigns slow down the instance? | Community
Skip to main content
A
Anonymous
January 21, 2016
Solved

Will having excessive trigger campaigns slow down the instance?

  • January 21, 2016
  • 2 replies
  • 2023 views

We have hundreds of active trigger campaigns  and I'm wondering if that is one of the reasons why we have a slow instance and batch campaigns take a very long time to execute.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Kenny_Elkington

    This is a somewhat complicated question.  Increasing the number of active trigger campaigns will always slow down trigger evaluation to some extent, which can introduce latency between, action, evaluation and flow execution.  This does not necessary mean that this will slow down flow execution significantly, as that is dependent on how many flow steps are being added by your trigger campaigns.  If there's a significant number of flows being triggered, then yes they will cause a slow down in performance of batch campaigns as trigger campaigns run at a higher priority than batch campaign by default if they:

    A) do not start with a wait step of five minutes or more

    or

    B) have flow steps other than change score in them

    This means that triggered flows will run before any batched flows.

    Your trigger evaluation can also get slowed down by having a higher number of triggers evaluating conditions which use "contains" or "not contains" as these are by far the slowest evaluations you can perform in triggers.  A large number(hundreds) can drag your trigger evluation and web activity data to a total slog.

    What does your campaign queue look like?  Are you seeing large numbers of trigger and high priority flow steps there on a regular basis?  Do you have a lot of web activity-triggered campaigns?  This could give you a high volume of flows which are executing ahead of your batch campaign flow steps.

    2 replies

    Josh_Hill13
    Josh_Hill13
    New Participant
    January 21, 2016

    In addition to what Kenny said, you can go to the Campaign Inspector to download all Triggers and decide if you can find ones that can be turned OFF (previously archived, or clearly old), or moved to batches.

    Kenny_Elkington
    Kenny_ElkingtonAccepted solution
    New Participant
    January 21, 2016

    This is a somewhat complicated question.  Increasing the number of active trigger campaigns will always slow down trigger evaluation to some extent, which can introduce latency between, action, evaluation and flow execution.  This does not necessary mean that this will slow down flow execution significantly, as that is dependent on how many flow steps are being added by your trigger campaigns.  If there's a significant number of flows being triggered, then yes they will cause a slow down in performance of batch campaigns as trigger campaigns run at a higher priority than batch campaign by default if they:

    A) do not start with a wait step of five minutes or more

    or

    B) have flow steps other than change score in them

    This means that triggered flows will run before any batched flows.

    Your trigger evaluation can also get slowed down by having a higher number of triggers evaluating conditions which use "contains" or "not contains" as these are by far the slowest evaluations you can perform in triggers.  A large number(hundreds) can drag your trigger evluation and web activity data to a total slog.

    What does your campaign queue look like?  Are you seeing large numbers of trigger and high priority flow steps there on a regular basis?  Do you have a lot of web activity-triggered campaigns?  This could give you a high volume of flows which are executing ahead of your batch campaign flow steps.

    Terms & ConditionsAccessibility statement

    Loading footer...