Symptom
The AFP output contains TLE data, but the archive or indexing tool cannot find BNG and ENG structured fields.
AFP_WORKFLOW_BUNDLE is enabled and still no named page groups appear.
Page-level TLEs are demonstrably present, yet customer and document boundaries are not recognized downstream.
Cause
The trigger for Begin Named Page Group (BNG) and End Named Page Group (ENG) records is a customer-level or document-level TLE.
A page-level TLE alone never creates the groups, no matter how correct it is; it indexes pages, not boundaries.
And the workflow-bundle switch is not the trigger either, despite its name suggesting grouping.
There is a second, quieter failure mode: the output queue's TLE search-key configuration can suppress a TLE that is perfectly correct in the application, so the design shows a TLE and the output stream does not contain it.
Fix
Place the required TLE at customer or document level, and configure the AFP output queue to include TLE and the related NOP records.
Set the queue's search key to ALL, or configure it to match the TLE search key assigned in the application.
Then verify at the byte level: generate a small AFP file and inspect the structured-field sequence around one customer and one document boundary.
You should see the BNG, the pages, and the ENG in order.
Final validation belongs to the archive consumer, not to a visual AFP viewer. A viewer shows pages; it does not prove that your archive system recognizes the group boundaries it will index by.
Verify the structured fields, not the switches
Three configurations produce the same archive symptom. AFP_WORKFLOW_BUNDLE does not create the groups. A page-level locator indexes pages but does not define customer boundaries. The queue search key can also remove a correct application TLE from the output stream.
Inspect the structured-field sequence to distinguish them.
This behavior is corroborated for the classic family; do not assume it maps onto current cloud-native output paths.