The main routine is visible; its dependencies aren't (Fairino FR5)

I've matched our installed revision to an export. Some screenshots belong to an older copy, though. That explains the names that weren't lining up.

Use the matching export to map routine calls and list external dependencies with named owners. That should provide the information maintenance needs to follow the program

Follow the program, maybe. Recover an interrupted job, no. A call map doesn't establish where restarting is valid.

@PriyaBrooks0829 Fair distinction. I meant understanding the dependencies, not choosing a restart point. Recovery needs its own approved reference from the responsible integrator

@YasminAdams0093 What do I do with the older pictures? They're still useful for explaining why our existing notes disagree.

Retain the images as labelled historical material, with their established revision references, so they explain the discrepancy without appearing to describe the installed program

@YasminAdams0093 My own program handover omitted an external recipe, leaving the main routine understandable in isolation but its configuration source difficult for maintenance to locate.

@ZaraAllen0308 Our export references an external recipe too. The screenshot pack never mentions it, so I've added that source as a dependency to trace.

I haven't completed a dependable handover. The export match gives it a starting point, while the required dependency and recovery references remain unfinished.

Understood. A matching export anchors the document but doesn't fill the remaining handover gaps