In some cases where it may seem that cputil is available, the GET job data route is able to successfully complete and send a response based on a token. However, if cputil is not properly installed on a environment (like with compatibility issues seen on alpine environments), the route is still returning a 200 with an empty receipt. To help diagnose and catch these issues earlier, we should check the file size of the receipt before sending it, and throw an error if it appears to be empty.
We should also add a check for jobData being undefined in addition to a null check to escape the route earlier.
In some cases where it may seem that cputil is available, the GET job data route is able to successfully complete and send a response based on a token. However, if cputil is not properly installed on a environment (like with compatibility issues seen on alpine environments), the route is still returning a 200 with an empty receipt. To help diagnose and catch these issues earlier, we should check the file size of the receipt before sending it, and throw an error if it appears to be empty.
We should also add a check for jobData being undefined in addition to a null check to escape the route earlier.