I had this problem at MMS and someboy else here in Microsoft just asked me about it. In case this is a more common thing that might be happening out there, I’ll drop this blog post out here to explain it and what the resolution is.
You create a SCSM- Orchestrator connector and sync some runbooks over.
You add a new folder in Orchestrator (underneath the one that you originally configured as the scope when you first created the Orchestrator connector) or a runbook somewhere in the folder hierarchy.
You run ‘Sync Now’ for the connector and the new runbooks don’t show up OR you open the SCSM – Orchestrator connector properties dialog and try to update the folder hierarchy and don’t see the child folders.
You double check the permissions for the connector run as account in Orchestrator and all seems OK. “What’s the problem?” you say as you tear out a clump of hair.
The problem may be that the Orchestrator permissions cache hasnt updated yet to grant the connector run as account user on the new folder/runbooks.
You can force an update of the cache by running this SQL query on the Orchestrator DB.
TRUNCATE TABLE [Microsoft.SystemCenter.Orchestrator.Internal].AuthorizationCache
Let us know if this works for you in the comments below.