I have race condition when acdl event is pushed and added as event type , the custom code block even first line of console log doesnt execute and it throws a timeout error

[KalaivaniL4]

In my website , I see a race condition rarely when the user land on first load rarely i could see my web sdk page load rule is not triggerring. So i created an rule checking whether the acdl,ecid and one trust is available and emitting an acdl event on its availability.But this rule checking throws a timeout error on a race condition first page load where it records a unique visitor but not the pageview.
We are triggerring that checking rule on acdl event pageloaded, but also throwing race condition and says custom code has been time out.
Any help how this can be fixed.
Note : Will this be caused as when acdl is pushed before launch library is not ready
please advise

[bjoern__koth]

Hi @KalaivaniL4 

by any chance, can you add screenshots? Having a hard time following your setup.

[KalaivaniL4]

this is the error which i am getting on a race condition, inside this custom code i have first line console log even that isnt printing.It didnt even get into custom code to emit pageload ready event which needs to triggered for page load rule

[Jennifer_Dungan]

Oh, so you are halting progress on tracking until users interact with your OneTrust logic... 

I don't think a timeout change here is the best option...

I am wondering if you should split up the logic... 

If the user is opted-in, run a rule that has an Opt-In condition on the DOM Ready or whatever page trigger you have. I would also add a second "Direct Call" trigger on this rule. Something like:

If the user is not opted-in, then the rule won't fire when the page loads, and if they are, then it will run.

Then, you need a second rule that is tied to the action of opting-in... when the user opts-in (which will be far past the DOM Ready state), you can call the Direct Call trigger using:

_satellite.track('opt-in-action');

So the user will opt-in, have the opt-in condition, and trigger the tracking rule...

Nothing is sitting there waiting for something to happen and timing out.

[KalaivaniL4]

We are not waiting for one trust login but we are trying to resolve when the user lands from campaign page sometime race condition occur where the timeout occurs and not triggering the page load rule. Hence they developed another rule to verify whether the adobe analytics ecid, onetrust, is ready then to emit an acdl event global pageload event ready which can resolve the timeout issue which is happening in the website, so hence unique visitor counts 1 and there is no pageview hit which 0 for few ecid hence created an rule to emit an event then to trigger the pageload event.

[Jennifer_Dungan]

Ok, I see... but since we don't have access to see your code, know how the pieces fit together or see it in action, this will be very hard to diagnose...

Have you reached out to your site developers? Maybe they can help with the coding and support the issue you are facing?

Or if you can provide more info about what is happening, we can try our best to help... but there's so many unknowns for us right now... 

Right now, all we can see if that there is a 30 second timeout.. and I can see an unresolved OneTrust banner... which is why I thought this was what you were waiting on (for the user to accept or reject)