Using Two Different AWS Lamdba Functions - Getting 404 on JobID Status

Greetings! We have an AWS Lambda function that posts a query, gets the status, and outputs the records returned into JSON files we add to an S3 bucket. To avoid timeouts in AWS Lambda, we've decided to split the POST and GET into two different functions. As soon as we used a separate function, we started getting a 404 job id invalid error when trying to get the JobID status. We are using the same authentication in the header for both. We've also used a REST client app via browser to try to get the info and the same result - 404. However, if I use the REST client to POST the query and then use the JobID returned to get the job status via the same REST client, we get results. What are we missing? Thanks!