wrong succession of actions in published rule | Community
Skip to main content
frankr83800809
Level 2
Jul 4, 2018 8:46 AM UTC
Solved

wrong succession of actions in published rule

Hi,

when configuring a new rule to fire a tracking request I set three actions:

1. Set Variables

2. Send Beacon

3. Clear Variables

After testing I see an Adobe Analytics request without any props or evars.

And when looking at the published rule it looks like:

1. Send Beacon

2. Set Variables

3. Clear Variables

How can I get this right?

Best,
Frank

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    thebenrobb
    thebenrobbAccepted solution
    Employee
    Jul 24, 2018 5:25 PM UTC

    We released a fix in our release this morning (2018-07-24).  In order to get things ordered correctly, you'll need to open your rule, make a change (you can change the order, then change it back to where it was, that counts), and save the rule.

    We are working on an automated process that will fix this automatically for all affected rules, but that will probably not make it into a release until next week, so those negatively impacted can fix it manually now.

    Technical details for those curious: under the hood, each action in a rule has an order.  There were some scenarios where the order was not being saved correctly.  Sometimes it didn't matter, and sometimes it caused your actions to appear in a different order than they were when you saved them (if you opened the rule again after save).  The fix waits for a rule to have a change, then when it is saved, it will normalize the order of all rule components, giving them each a new order value based on what you've specified in your rule.

    View reply

    12 replies

    thebenrobb
    thebenrobbAccepted solution
    Employee
    Jul 24, 2018 5:25 PM UTC

    We released a fix in our release this morning (2018-07-24).  In order to get things ordered correctly, you'll need to open your rule, make a change (you can change the order, then change it back to where it was, that counts), and save the rule.

    We are working on an automated process that will fix this automatically for all affected rules, but that will probably not make it into a release until next week, so those negatively impacted can fix it manually now.

    Technical details for those curious: under the hood, each action in a rule has an order.  There were some scenarios where the order was not being saved correctly.  Sometimes it didn't matter, and sometimes it caused your actions to appear in a different order than they were when you saved them (if you opened the rule again after save).  The fix waits for a rule to have a change, then when it is saved, it will normalize the order of all rule components, giving them each a new order value based on what you've specified in your rule.

    Translate
      KRAZ
      Level 3
      Jul 24, 2018 11:30 AM UTC

      Jantzen.Belliston do you have any updates? The end of the week passed by and still, the error persists. I also opened a ticket 3 weeks ago and there is no update on the topic.

      For me, this is really a highly time-consuming bug which also caused a lot of errors in my tracking so far!

      Translate
        jantzen_b
        jantzen_b
        Employee
        Jul 16, 2018 7:16 PM UTC

        Hey Everyone,

        Thanks for sharing all your feedback on this. It definitely is a bug and the product team is aware of it. They are hoping to have a fix pushed out later this week.

        Thanks,
        Jantzen

        Translate
          thomas_amsler
          Level 6
          Jul 11, 2018 12:24 PM UTC

          There is another discussion regarding this issue: Potential bug- switching action order

          It is really anoying to have to reopen each rule again, after you clicked save as it may not have saved the order you saw when you clicked save. I hope this gets fixed soon.

          Translate
            tuckercampbell
            tuckercampbell
            New Participant
            Jul 10, 2018 8:13 PM UTC

            I'm also experiencing this issue. It is not exclusively when adding new actions but also when you edit existing actions. My clear variables seems to move automatically in front of my send beacon action causing none of set variables to pass. Even when trying to reposition the clear variable back in it's final place it pops back in the automatically positioned order. Thanks for getting this resolved.

            Translate
            jantzen_b
            jantzen_b
            Employee
            Jul 9, 2018 2:19 PM UTC

            Thanks for the tip. When opening the ticket with Customer Care, please reference this thread so the agent can have the context provided here.

            Translate
            KRAZ
            Level 3
            Jul 9, 2018 2:15 PM UTC

            Same Bug here...it only happens if you have already some Actions then add new ones and click on save. The freshly added ones always go first in the order.

            Translate
            jantzen_b
            jantzen_b
            Employee
            Jul 9, 2018 2:08 PM UTC

            Please open a customer care ticket by emailing clientcare@adobe.com. They can open a bug with our engineering department.

            Thanks,
            Jantzen

            Translate
            frankr83800809Author
            Level 2
            Jul 9, 2018 8:17 AM UTC

            Thanks Reyhan, I will inform Adobe about it.

            Best.

            Translate
            Reyhan_Sadaka
            Reyhan_Sadaka
            Level 2
            Jul 6, 2018 3:04 PM UTC

            I just tested in my instance, taking a rule that had been working. I added some values to the "Set Variables" call and I'm now seeing the same issue where "Send Beacon" is happening before "Set Variables". I did not change the ordering at all.

            This seems like it's an issue with Launch itself - something in the compiling and building of the rules?

            Translate
              Show more replies
              Terms & ConditionsAccessibility statement

              Loading footer...