Name workflow outputs so a later run can find them

A reusable workflow output name should identify the subject, output type, and date or version. Use a stable pattern such as customer-summary_2026-10-01_v2, but avoid embedding secrets or unnecessary personal data in filenames. Record where the file is stored and which run produced it. If the workflow retries, choose whether to overwrite safely or create a new version to prevent duplicates. A descriptive name helps only when the output can also be traced to its input and owner.