Phoenix reportback endpoint broken.

[DFurnes]

BUG

Current Behavior

The Phoenix reportback endpoint seems to have broken in the v2.8.4 release.

Northstar's reportback endpoints (which rely on the Phoenix /campaign/:nid/reportback functionality) have been failing since yesterday's 4:28pm staging deploy, and Gambit errors were reported by @aaronschachter in Slack this morning.

Desired Behavior

This endpoint should return a string with the Drupal reportback ID, like this:

["127"]

Steps to Replicate

It seems like any API call to this endpoint returns the following response: Well, it seems like at least some subset of requests return this (Runscope tests on Northstar QA, and my manual tests on both staging & post-deploy production).

null

I'm not sure whether the data is still persisted when this error occurs.

Why This Matters

Northstar (for the mobile app) and Gambit both rely on this endpoint.

Countries Affected (optional)

…

OS/Browser (optional)

…

Relevant Screenshots + Links

• Example Runscope failure

[DFurnes]

@chloealee has verified that Gambit SMS reportbacks still work, and I just tested the mobile app and everything seems to work as expected. I can't explain why the Runscope exceptions seem to still be occurring, but this is probably a false alarm.

[DFurnes]

The related Runscope test was running against the "Space Jam" campaign on staging, and seemed to be causing trouble with an excessive number of reportbacks. I wonder if that's related to why this endpoint is broken here.

Disabled the Runscope test for now since it's not providing any useful new information.

/cc @mshmsh5000

[mshmsh5000]