Juniper Wharf support asked why ID108 is missing from its Zinc queue. Repair the supported prefix query, inspect the returned identity and warning, and finish with the actual connector/population verification needed in a real environment.
Juniper Wharf’s queue looks empty for Zinc inspections even though the source includes a known late request. The app uses a lowercase expression against the supplied SharePoint-style profile and a small local row cap. Investigate where the filtering actually runs before blaming the source record.
Repair the query in connected steps, then expose the returned identity and warning state as evidence. The final reasoning must explain the original prefix boundary and recommend the real connector and source-population checks still needed. A successful local boundary test is useful, but it cannot support an unmeasured claim about every production record or remote response time.