Manifest File Names Not Matching in Responses

[djbusby]

Hey, so the system used to respond with the Manifest ID in the PDF Filename.LIke you can see from the first two attachments.This feature is how systems are able to map the resulting manifest document back to the original upload.Especially important when there are many requests to CCRS in-flight, and we're waiting so many hours for the response.

But on April 1st we had 31 responses for manifest upload that all had the same filename in the response:'Manifest_11150385124885009_20250401021504.pdf'The contents of the manifest were correct, and the ID printed in the footer was correct.But the filename didn't match -- and it usually does.And it's quite odd that it happened, with the exact same filename, for dozens of manifests.

I'm not sure if it's going to happen to more.
We've got uploads into CCRS from yesterday that are still waiting on the response (~20h)

[djbusby]

This was assigned as IN0002148 on 2025-04-04.

[djbusby]

On 2025-04-08, I got a notice from the LCB where they called it a minor issue and that nobody else is having the problem.

[djbusby]

My theory is that it IS affecting other users in the space, they just don't complain to the LCB because they know the LCB won't actually change anything -- so why waste effort? Additionally, the other vendors in the space appear to be using the Contingency Manifest (you'd have to, the Manifest's take 24+ hours to arrive).

But this issue is still happening, the filenames are all scrambled. And there is no way the system would only be scrambling data for just us -- that's just now how software works -- unless the LCB has singled out OpenTHC (becuase we complain too much?)

[djbusby]

Something else to notice here is that these emails are sent to both licensees to the transaction as well. So, they are each receiving manifest files that do not have matching filenames. Not sure how that will impact their organization and ability to track data. Youtube incoming.