Hey @joe.roddy,
With the release of v4.28.4 of Next.js Runtime, we’ve reverted the change of switching to individual function for each API route. This should solve the problem you’re seeing here as well as in the other thread. Let us know if it works.