What does “Partial” mean in Analyze?
Partial is intentionally narrower than Unsupported. It means the product recognizes the pattern and has some conversion path or placeholder strategy, but that path is not yet something you should treat as zero-review automation.
Partial is a review signal, not an automatic blocker
Many workflows with a small number of partial items are still strong export candidates. A partial step can mean the product knows the pattern but wants you to confirm connector settings, task strategy, template assumptions, or a premium action choice after import.
This is different from Unsupported, which means there is no trustworthy conversion path yet and the step should be treated as manual rebuild territory.
Not all partials carry the same risk
A partial HTTP action that already has a clean method and URI is very different from a partial complex database query with joins and vendor-specific functions. The Analyze screen is most useful when you read the note next to the partial, not just the status color.
Repeated partials often point to one missing mapping family. For example, an approval-heavy workflow may show many partial rows that are really one approval pattern repeated throughout the process.
- Low-risk partial: connector or import review likely
- Medium-risk partial: best-effort action with post-import validation
- High-risk partial: manual conversion likely for the core logic
Use Partial to plan the next action
If the partials are configuration-related, move into Required settings and see whether they clear. If the partials are concentrated in one advanced pattern, decide whether this workflow is still worth exporting now or should stay in a manual queue.
The product should help you make that decision faster. It should not pretend every partial is solved when it is not.