Closed heidimok closed 7 months ago
I believe this issue has been resolved from previous changes. Looking back through the historical errors, they seem to be cases where the wrong UUID was being used to refer to a Campaign, but we've made some changes since to address that sort of issue. In any event, I can't replicate it by navigating through the MI. The only way I can get the error again is by going to the bad URL directly.
I will make a change to return a 404 in this case rather than 500 error, since a missing Campaign shouldn't throw a non-descript error.
Context
Upon merging the new MI workflow into staging, we ran a Sentry test to catch issues. This is one source of errors found.
Problem
There's an error trying to access the published view for a certain campaign (not sure what's going on there yet). Will need to dig in a bit to explore the problem.