After switching some serverless REST APIs to serve...
# seed
d
After switching some serverless REST APIs to serverless-stack HTTP APIs… I don’t see Seed.run issues being created for 500 errors. Do I have to enable this somehow?
The Lambda Logs show a red error
f
Leaving a note here for others, it’s an issue with CloudWatch Logs where it sometimes fail to forward the logs for the very first invocation to it’s subscribers and CloudWatch Insights.
We pushed out a fix to work around this issue in Seed.