A automation where each page that was edited before certain time will be moved below different page
Asked by Nikhil Vichare:

I want to create an automation in which:

1. Gather pages last modified before 1st January 2020.
2. Move all those pages under a page that is already created.

I am unsure why it is giving an error "Incompatible Components" to move those pages.

Edit: I am adding SS for reference, I know why it isn't working. I want to know if it is feasible.

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/335244i4C30C8244EB7FC24/image-size/large?v=v2&px=999 "image.png")


Answers:
author: Shawn Doyle - ReleaseTEAM
body: To add to [@Aron Gombas _Midori_](/t5/user/viewprofilepage/user-id/502447) answer, you need to add something that returns the set of pages. Multiple ways to do it, here is an example of adding the page branch.

![automation.png](https://community.atlassian.com/t5/image/serverpage/image-id/335383iF55032B6F007F3CE/image-size/large?v=v2&px=999 "automation.png")![pagebranch.png](https://community.atlassian.com/t5/image/serverpage/image-id/335382i6F31CD54566A247A/image-size/large?v=v2&px=999 "pagebranch.png")


author: Aron Gombas _Midori_
body: You should paste a screenshot of the rule so that the community members can review this. Without that it is hard to tell what is the reason of the error.

comments: author: Nikhil Vichare
body: Done


author: Aron Gombas _Midori_
body: The problem is, I think, that the Scheduled trigger will not "provide" pages to the subsequent components.

Solution: after the trigger, you need to add another component that provides pages.

(I think you would want to periodically run a CQL search something like "lastUpdated \< 2020-01-01" to collect the pages and then you can remove the "if" test.)


author: Nikhil Vichare
body: Thanks [@Aron Gombas _Midori_](/t5/user/viewprofilepage/user-id/502447) and [@Shawn Doyle - ReleaseTEAM](/t5/user/viewprofilepage/user-id/815120) , the solution worked for me. You have been a great help. Thanks a lot.

comments: author: Aron Gombas _Midori_
body: [@Nikhil Vichare](/t5/user/viewprofilepage/user-id/5273825) The "archive" automation has its own limits in Confluence Automation.

If you reach those and look for something more scalable and eventually "more intelligent", then make sure you try the [automatic status tracking](https://www.midori-global.com/products/better-content-archiving-for-confluence/cloud/documentation/track-the-content-status) (which gives you access to CQL searches, macros, notifications, reports) and [automatic archiving features](https://www.midori-global.com/products/better-content-archiving-for-confluence/cloud/documentation/configure/automation-schemes) of the [Better Content Archiving](https://marketplace.atlassian.com/apps/123/better-content-archiving-and-analytics-for-confluence?hosting=cloud&tab=overview) app.

Related to your use case, here is an automation scheme which contains 2 automations. The first will archive all contents in the "To archive" status weekly on Sundays (midnight), while the second will delete all contents in the "To delete" status 2 hours later:

![configure-automation-scheme-cloud.png](https://community.atlassian.com/t5/image/serverpage/image-id/335570iE5E2CDEA1F36F5AC/image-size/large?v=v2&px=999 "configure-automation-scheme-cloud.png")

The two together give you a simple, but flexible page retention mechanism.

*(Discl. it is a paid and supported app developed by our team. Free for 10 users!)*


author: Nikhil Vichare
body: Hey [@Aron Gombas _Midori_](/t5/user/viewprofilepage/user-id/502447) , thanks for the suggestion. I think most of my usecases are covered by automation created before. But in future if I require, I will definitely check this out.


Tags: cloud

confluence-cloud