Troubleshooting Packages

The expected package is missing

Check:

• whether you are in the correct configuration
• whether package sync has already run for this tenant
• whether the package is really missing, or only not matching the search term

The package exists, but the artifact count looks wrong

Typical causes:

• artifact sync has not caught up yet
• the package contents changed recently in CPI
• the current inventory is partial because downstream sync is still running

Labels look outdated or inconsistent

Check:

• whether labels were maintained manually and never updated
• whether different operators use the same naming pattern
• whether the issue belongs to package classification rather than runtime data

I need more detail than the package view provides

That usually means the next step is Artifacts, not another package action.

Move on when you need:

• deployment state of one iFlow
• version or hash comparison
• where-used or metadata details

When to use the technical docs

Switch to /sysdocs when you need:

• package storage and sync flow
• module ownership of the popup
• frontend and backend boundaries
• deeper relation between packages and artifacts