Assurance events stuck on Post process status "Queued" | Community
Skip to main content
Level 2
February 1, 2024
Question

Assurance events stuck on Post process status "Queued"

  • February 1, 2024
  • 1 reply
  • 1617 views

Assurance events are coming through but get stuck on "Queued" and never become "Processed" so we're unable to view the "Post processed and request details". It has affected both our Android and iOS implementations. Is there a current issue with Assurance?

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

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
February 2, 2024

Hmm I will be doing mobile testing tomorrow.. this doesn't bode well...

 

I wonder if this is connected to the Experience Debugger not returning Post-Processed data for at least the last week.

 

I think both of these need to be logged with Client Care.

Level 2
February 2, 2024

Please let me know if there's anything I can do on my end and how I can track the issue. Thank you!

Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
February 2, 2024

Do you have access to the Support panel in the Admin Console to log tickets?

 

I checked our Griffon logs, one of my colleagues was testing this morning and there is post-processed data..  Unless the issue started in the afternoon / evening (my time zone), this issue may not be affecting me.. and without a sample of the issue I can't log an effective ticket for engineering to investigate (they really need to see the issue to try and dig into the logs).

 

While I can log a ticket for the Cloud Debugger (since I can replicate that issue and provide logs and details), the two issues may not be connected as I originally suspected.

 

If you cannot log tickets for your company, I think you should work with your admin person to log the ticket on your behalf.

 

All I can say is "good luck, and I hope the issue self resolves, or that support is able to fix it quickly".

 

I will confirm on my end tomorrow that our implementation is still working.