19/08/2026 4:24 pm
Topic starter
Community
Connect with us and enhance your M-Files experience using Extension Kit for M-Files. Here is how to get started.
Notifications
Clear all
0
Have a rule in Orchestrator that shall run every 15 minutes and trigger a Property Operations rule which then changes one boolean property from True to False or the opposite.
This is supposed to invoke a check out - check in process which in turn will trigger a Managed Properties rule in Compliance Kit, and that will then trigger other Property Operations rules in Ext.Kit.
The chain of events work fine when the boolean property is changed manually. If successful the same objects will not fit the filter settings at next run, only new objects will be handled.
The rule starts as planned, it finds the relevant objects, but it skips changing the setting. The log says:
| Out of 33 objects that were found, execution succeeded for 0 objects, failed for 0 objects, was skipped for 33 objects and was not run for 0 objects. |
There does not seem to be any errors neither in the Ext.Kit log nor in the server event log, but nothing happens with the selected objects.
What does it mean that execution was skipped?
What might cause this behavior?
Topic starter
19/08/2026 6:34 pm
Tried to replace the Compliance Kit rule with a direct Property Operations rule in Extension Kit. The latter was then orchestrated with the same filter as used before. The result was still all objects skipped, no errors....!
2 Answers
0
19/08/2026 7:33 pm
Topic starter
Realized that one reason was my use of the wrong property reference. Had 2 lookup properties for the same reference (1 multiselect, 1 single). Even after changing that the task is still skipped when using Orchestrator, but not when run one by one. Strange!
0
20/08/2026 6:55 am
Hi Karl,
Could you please share the configuration of the Orchestrator rule and the first PO rule in the chain? We’ll inspect the configuration and get back to you as soon as we can. It would also be very helpful if you could send us a screenshot of one of the objects you’re trying to set, so that we can see its structure and check for any potential issues.
Best regards,
Nika
Topic starter
21/08/2026 2:33 pm
Sorry @nikatilic, I am short of time these days. Had to find a quick solution and decided to drop the Orchestrated rule and create a new Property Operations rule based on a certain event in one object type that has a relation to the other object type which is then used as target. This seems to work. Can't spend more time on this for now.
