Timeout Error on "Send Beacon" Action in Page Rule | Community
Skip to main content
S
SaurabhPathakRa
Level 2
March 11, 2026
Question

Timeout Error on "Send Beacon" Action in Page Rule

  • March 11, 2026
  • 2 replies
  • 60 views

Body:
Hello everyone,

I’m encountering an issue with a Page Rule in Adobe Analytics. The rule is configured with:

  • Event: OneTrustGroupsUpdated
  • Action: Send Beacon

However, I consistently receive the following error:

 

Failed to execute "Send Beacon" for "Adobe : Page Rule" rule. A timeout occurred because the action took longer than 5 seconds to complete. Error: A timeout occurred because the action took longer than 5 seconds to complete.

 

Since the rule only has the event and the beacon action, I’m unsure why it’s timing out.

Has anyone else faced this issue, or do you know what could cause the beacon to exceed the 5-second limit? Any guidance on troubleshooting or optimizing this setup would be greatly appreciated.

Thanks in advance!

 

2 replies

kaush1889
kaush1889
Level 3
March 11, 2026

Seems like a race condition between OneTrust and AA. First thing I will check is the rule ordering and also enable debug to see if anything shows up:
_satellite.setDebug(true);

S
SaurabhPathakRaAuthor
Level 2
March 11, 2026

​@kaush1889 I tried that earlier. I also tried to reload my page after consent is granted. Still same error popped up 
 

 

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
March 11, 2026

Hi,

 

What does your event look like? Is it some custom code that starts running when the page loads and waits for something from OneTrust?

 

If the only action is “send beacon”, its unlikely the hold up is there, but you might need to find a cleaner way to listen for the OneTrust consent to be decided?

 

I assume this only fails on the first load, when you are waiting for the User to make a choice, and that after they have made their decision, subsequent pages are fine?

S
SaurabhPathakRaAuthor
Level 2
March 12, 2026

​@Jennifer_Dungan , 

This is the current setup I have for the event. 
 

I also tried with just dom ready to test if normal page load triggers the action of sending beacon, but still getting the below error. 
 


 

Rule setup 

When I reload the page repeatedly, the beacons are still not sent to Adobe.

I noticed a strange behaviour on the site: when I am inactive for a while (10 min) and then return to the page and reload it, the page load rule gets triggered, and data is sent. However, if I reload the same page again afterwards, it produces the same error.
 

 

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
March 12, 2026

This might sound funny, but I used to have a lot of problems with Launch’s “Custom Event” trigger.

 

I now do custom code for JS Events that I want to listen for.

 

Can you try using the following:

window.addEventListener('OneTrustGroupsUpdated', function (e) {
  trigger();
}, false);

 

Just make the trigger Custom Code, and paste the above in the Editor:

 

See if this works better for you? If you still have issues, we’ll go back to the drawing board… but I use this for events that can happen at any time on the page, and haven’t had issues on my setup.

Terms & ConditionsAccessibility statement

Loading footer...