Gravity Flow 3.1.1 fixes a PHP fatal that could occur when an outgoing webhook used GET while a body remained configured. The visible editor can preserve a body field even though GET integrations normally need query parameters, creating an invalid combination that fails at workflow execution time.
Use this when a Gravity Flow outgoing webhook step fails, a workflow stalls after submission, PHP logs mention the webhook add-on, or an endpoint changed from POST to GET without clearing its body mapping.
Quick answer
Pause the affected step, record the exact failure and entry IDs, and inspect method, URL, query mapping, headers, body configuration, authentication, signature, timeout, and retry history. If the destination truly requires GET, move supported values into encoded query parameters and remove the body. If it requires a structured payload, use the documented POST method instead. Update Gravity Flow to 3.1.1 or later, run a synthetic request against a controlled endpoint, then replay only entries whose downstream outcome is known and deduplicated.
Test scenarios to run
Run the same controlled fixture across these branches. Write down the expected result before testing so a surprising response is easy to identify.
| Scenario | Fixture | Expected result |
|---|
| GET plus body | Legacy stored config | No fatal after cleanup |
| GET plus query | Encoded values | One accepted request |
| POST plus JSON | Structured payload | Expected schema |
| Lost response | Same entry ID | No duplicate effect |
Diagnostic table
Use this table to connect the observed behavior to evidence and a verification step.
| Action | Evidence | Verification |
|---|
| Pause and preserve evidence | Record Gravity Forms, Gravity Flow, PHP, step ID, entry IDs, HTTP method, URL, query parameters, body mapping, headers, authentication, signature, timeout, and retry policy. | GET requests carry only intended query values and no stale body configuration. |
| Choose correct HTTP semantics | Inspect the editor and stored step configuration because a body may remain after a method change even if the current screen does not make the combination obvious. | POST requests send the documented body and signature once. |
| Update Gravity Flow | Correlate PHP fatal time, workflow note, request log, destination access log, provider record, and entry status before deciding whether the request reached the recipient. | PHP, workflow, destination, and provider logs correlate by one synthetic ID. |
| Test a controlled endpoint | Test GET with encoded query values, POST with JSON, empty optional values, special characters, authentication failure, timeout, 429, 500, and a lost response. | Failed historical entries are reconciled before any replay. |
What to check first
- Record Gravity Forms, Gravity Flow, PHP, step ID, entry IDs, HTTP method, URL, query parameters, body mapping, headers, authentication, signature, timeout, and retry policy.
- Inspect the editor and stored step configuration because a body may remain after a method change even if the current screen does not make the combination obvious.
- Correlate PHP fatal time, workflow note, request log, destination access log, provider record, and entry status before deciding whether the request reached the recipient.
- Test GET with encoded query values, POST with JSON, empty optional values, special characters, authentication failure, timeout, 429, 500, and a lost response.
- Update, remove invalid GET body data, add idempotency where the destination supports it, and replay only entries with a known safe outcome.
Field notes
- Write the pass condition before changing anything and keep one repeatable synthetic fixture for the full test window.
- Record exact versions and UTC timestamps because deployments, caches, retries, scheduled actions, and background jobs can change the evidence.
- Test the public path and the stored server-side result, not only an admin preview, isolated command, or API response.
- Repeat verification after the relevant cache, queue, cron, webhook, and observation window has completed.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
curl -sS -G --data-urlencode 'entry_id=GF-1042' --data-urlencode 'status=approved' https://endpoint.example.test/hook
curl -sS -X POST -H 'Content-Type: application/json' -d '{"entry_id":"GF-1042"}' https://endpoint.example.test/hook
Why this usually happens
- A workflow changes method but retains old body configuration.
- The editor displays a body control for a method that should not use it.
- A fatal occurs before the workflow can record a useful remote response.
- Blind replay duplicates a request that reached the destination before the local failure.
Decision rule
Resume the workflow only when the method and payload shape agree, synthetic failures are logged without a fatal, and a replay cannot duplicate a downstream action.
Production verification checklist
- GET requests carry only intended query values and no stale body configuration.
- POST requests send the documented body and signature once.
- PHP, workflow, destination, and provider logs correlate by one synthetic ID.
- Failed historical entries are reconciled before any replay.
Safe fix order
Use a sequence that makes each result easy to prove. Stop when new evidence changes the scope or owner of the problem.
- Pause and preserve evidence
- Choose correct HTTP semantics
- Update Gravity Flow
- Test a controlled endpoint
- Replay with reconciliation
Mistakes to avoid
- Changing production before recording exact plugin versions, UTC timestamps, a stable fixture, the expected result, and a tested rollback point.
- Treating one successful screen as proof while stored records, logs, queues, caches, emails, APIs, and downstream systems remain unchecked.
- Testing only as an administrator instead of using the role, device, locale, cache state, payment state, and failure branch that customers reach.
- Leaving temporary exclusions, debug output, test accounts, broad permissions, or one-off repair code active after verification.
Questions teams ask during testing
Can I run this directly in production?
Begin with read-only evidence and use staging for package, database, checkout, form, permission, or security changes. If a production canary is necessary, make it identifiable, reversible, monitored, and unable to expose personal data or charge a customer.
How do I avoid a false positive?
Repeat the same fixture with the same versions, role, URL, locale, cache state, and integrations. Compare browser, stored, API, and log evidence instead of relying on one screen.
What should the evidence packet contain?
Keep UTC time, exact versions, synthetic record ID, expected result, actual result, relevant log lines, change made, rollback point, owner, and final verification. Redact secrets and personal data.
When is the test complete?
Close the work when the primary path passes, failure branches are understood, stored and downstream records reconcile, temporary changes are removed, and monitoring covers the next update.
What to tell the client or owner
Give the owner a concise packet with the affected workflow, exact versions, UTC test time, fixture ID, expected result, actual result, key logs, change made, rollback point, final result, unresolved risks, owner, and next review date. Remove credentials and personal data before sharing it.
When HandL WP should help
Bring in help when this affects leads, checkout, search visibility, security, paid media reporting, or a client production site. HandL WP can trace the issue through WordPress, hosting, cache, tracking, and Search Console, then verify the workflow after the technical fix.
If this is active on a production site, have HandL WP repair a Gravity Flow webhook.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references