I am trying to troubleshoot Triggers and the pipelined process using the help at How to use Experience Cloud Triggers with Adobe Campaign Classic
It talks about a "pipelined status page" (No triggers are retrieved > Step #4 Look for errors in the pipelined status page. trigger-discarted, trigger-failures should be zero.)
Can you tell me where I find this status page in the client UI?
Solved! Go to Solution.
After searching the documentation page you linked, I think the status page is this: http://INSTANCE/pipelined/status
INSTANCE should be replaced with the ip address from your instance and you should use port 7781.
See screenshot from the page:
After searching the documentation page you linked, I think the status page is this: http://INSTANCE/pipelined/status
INSTANCE should be replaced with the ip address from your instance and you should use port 7781.
See screenshot from the page:
Did you manage to get the URL to work? Reason I ask is Adobe engineering said the status page was only ever made available in an internal Adobe release version and was never released in a GA release. I could never get it to work, even after getting pipelined set up properly.
It could also be because it was a hosted version of the product and the port required was not opened in Adobe's AWS. Hard to tell what the real reason was.
Apparently it should not have been put in the public documentation (and still hasn't been removed). So I'm curious if anyone has ever seen this page work in the wild or in an on-prem install?
Views
Replies
Total Likes
Yes I was able to visit this page when replacing instance with our ip address we use for our production environment.
I also checked with Adobe Support and they confirmed it is the status page they refer to.
However I was looking for the queue size of the pipeline but that variable wasn't available on that page.
LeonieSwart - do you have an Adobe hosted version or an on-prem install?
Views
Replies
Total Likes
We have an on-premise install.
Views
Replies
Total Likes
Thanks LeonieSwart - Now I think our issue was an Adobe port blocking issue on a hosted instance rather than some other reason I was told by support. Appreciate the response!
Views
Replies
Total Likes
Views
Likes
Replies