Hi all,

I have an issue with my content organizer rules. They trigger on certain contenttypes in combination with a field that has a yes/no value. When I manually create a document and select the right conditions the content organizer rules work as promised. Now I have a workflow that checks if a document is approved before setting the field with yes (Conditions are met). However, the content organizer rules timerjob doesn't seem to work. Even if I manually start the timerjob nothing happens (I don't spot any problems in ULS, it just runs). If I open this document and save without change the document gets routed immediately.

The timerjob is run by the "sp_farm" account so that should be fine. Any ideas?

Thanks in advance.

Hi Mango,

I tested the same scenario per your post in my environment, and the documents had been routed to the right place after the workflow completed.

For this issue, I recommend to check the things below:

1. Make sure that the field for the document meets the Content Organizer rule.
2. Make sure that you have run the corresponding timer job for the web application where the library exists.
3. Please provide more details about your workflow for reproducing the issue.

Best regards,

Victoria

Hi Victoria,

Thanks for replying.

1. The document meets the content organizer rules requirements. If I open the document and save without making changes, the content organizer rules trigger and reroute te document correctly. I also tested with removing all content organizer rules requirements to the minimum of only matching the contenttype.

2. I run the timerjob "Content organizer rules" and changed it from running 1 time a day to every 15minutes. I also checked the ULS log and can see that timerjob runs through the site the library is on. No errors, but nothing happens either.

3. The workflow is actually pretty basic. It waits for the approvalstatus to change to "approved". (Sorry if this is not actually how its called, i translate from dutch as that is what i use) When the requirement is met a custom field will be changed from "no" to "yes". This "yes" is the trigger for content organizer rules to reroute te document. If I create a document with this custom field already on "yes" the document will be immediately rerouted, but not when the workflow does it.

I wouldn't be surprised if the content organizer rules timerjob didnt function properly at all and the workflow is not at fault here.

I have temporarely resolved the issue by adding to the workflow that when the custom field is changed to "yes" the document will be looped back the dropofflibrary. This triggers the dropoff to immediately reroute the document correctly, but I am still unsure why the timerjob does not function.

Thanks in advance.

Hi Mango,

Per my knowledge, the content organizer rule works on the drop off library.

When you have enabled Redirect Users to the Drop Off Library in content organizer settings, then the documents uploaded to library with one or more organizer rules pointing to them will be uploaded to drop off library first.

And after that the content organizer rules will be executed when the documents in drop off library meet the condition of the organizer rules.

So when we upload a document which meets the condition of a rule, it will directly route the document to the corresponding library.

For existing documents in the library, the document will be stored in the library without routing to the corresponding library as they are not routed to drop off library first.

So we need to route the documents to drop off library first if we need to route the documents.

Best regards,

Victoria