Core has no hard restriction on the maximum file size that you can attempt to process. There is an upper bound to what Core’s parser can process successfully, but that depends on a number of factors.
|File size||~500 MB [^1]|
|Largest single transaction set within a file||~130 MB [^2]|
If your file fails to parse without a guide, try it again with a guide; in certain cases, using a guide will allow for slightly higher limits. In the very unlikely event that it still fails, drop us a note – we can help you implement a workaround that allows for virtually unbounded transaction set and file size. If you’re able to provide a failing sample, our engineers can use it to ultimately improve our parsing logic to handle the file without a workaround.
[^1] An EDI file can contain multiple interchanges, and each interchange can contain multiple transaction sets. The limit of what Core can process is generally dictated by the size of the largest EDI transaction set within the file, not by the file size itself.
[^2] This can vary depending on the complexity of the transaction set, complexity of the guide, the number of elements in the transaction set, and other variables.
Have an idea for something we could improve? Page not clear? We love feedback - send us a message.