Hi All,
I have set an expiration date for an asset. In the timeline I was able to see that asset is expired but the asset is still in published state.
Not sure why the ootb is not triggering ootb workflow for Unpublishing the asset once it expires.
Thanks in advance
Views
Replies
Total Likes
I asked our team to look here. Are you seeing any error messages.
Views
Replies
Total Likes
Thanks Scott for looking into it. I am seeing below errors not sure if its related.
09.01.2019 22:52:58.145 *ERROR* [sling-threadpool-378a0770-6f16-4526-9910-726f176b4194-(apache-sling-job-thread-pool)-471-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish Error while sending request: java.net.ConnectException: Connection refused: connect
09.01.2019 22:52:58.145 *ERROR* [sling-threadpool-378a0770-6f16-4526-9910-726f176b4194-(apache-sling-job-thread-pool)-471-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish ------------------------------------------------
09.01.2019 22:52:58.145 *ERROR* [sling-threadpool-378a0770-6f16-4526-9910-726f176b4194-(apache-sling-job-thread-pool)-471-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish Sending message to localhost:4503
09.01.2019 22:52:58.145 *ERROR* [sling-threadpool-378a0770-6f16-4526-9910-726f176b4194-(apache-sling-job-thread-pool)-471-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish >> POST /bin/receive HTTP/1.0
09.01.2019 22:52:58.145 *ERROR* [sling-threadpool-378a0770-6f16-4526-9910-726f176b4194-(apache-sling-job-thread-pool)-471-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish >> Action: Delete
Views
Replies
Total Likes