CloudPage Production Incident
Triage a public CloudPage that is erroring, writing bad data, redirecting incorrectly or receiving malformed context.
Evidence tier describes my hands-on relationship with the content. Official sources describe platform contracts/documentation. Production observations should not automatically be treated as official limits.
Reproduce with the exact URL/context
Distinguish direct access, encrypted CloudPagesURL flow, form POST and external-link behavior.
Inspect RequestParameter inputs
Check required parameters, empty values, unexpected actions and record identifiers before touching downstream logic.
Separate read failure from write failure
Test lookups independently from UpsertData/UpdateData/API calls so the failing layer is visible.
Check repeated-submit behavior
Refresh/back-button/retry should not create uncontrolled duplicate side effects.
Review public exposure
Ensure credentials/secrets are not in client-side code and that error output does not leak sensitive context.
Verify redirects and final state
After a successful write, confirm the user sees the correct result and the target DE/system reflects it exactly once.
Add a negative test
Turn the incident into a test for missing, malformed and replayed parameters in the next deployment.