No components marked as affected
Resolved
This issue looks to be resolved, and we are no longer seeing Edamam returning errors. We have reached out to Edamam to gather more info here.
Investigating
Our nutrient database vendor (Edamam) appears to be down, which is causing internal server errors when loading food entries and/or creating a new food entry involving specific nutrients. We are continuing to monitor.