A finished Results log can mark a row Blocked even after earlier review. Read the final outcome reason, because the actual write must still satisfy the current account, source and permission conditions.
- Open the finished batch and filter by the blocked result.
- Compare the row’s current reason with its earlier check and your intended decision.
- Resolve the stated condition through the appropriate workflow before attempting a corrected import.
Do not assume a row was added because it once appeared Ready. The final result is the evidence of what the import actually did.
Check for changes during the batch
A period can become protected, access can change, or the source can conflict with work completed elsewhere. Investigate the specific result instead of repeatedly pressing import from an old screen.
Keep successful rows from the same batch identifiable. If you prepare another file for blocked rows, include only the intended unresolved activity and review overlaps. For support, provide the filename, account, source line and final reason so the failure can be traced without recreating the entire period.
Was this article helpful?
Tell us whether this answered the question you came with.