[DIAG] Surface Airtable error in MP-email response#866
Draft
UFO-101 wants to merge 2 commits into
Draft
Conversation
Diagnostic patch only — include the underlying Airtable error text in the response body when the write fails. The endpoint is currently returning 500 in production and we don't have function-log access to see why. Revert immediately after capturing the error.
✅ Deploy Preview for pauseai ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Temporary diagnostic patch. The UK MP email endpoint is currently returning 500 in production with an opaque message; this surfaces the underlying Airtable error text in the response body so we can identify the cause without function-log access.
Test via the Netlify deploy preview's
/uk-email-mpform — submit, then read the response body in the network tab. Revert immediately after.