Most of the "Gravity Flow is broken" problems we've chased turned out to be one of these. Add yours in the replies and we'll keep this thread as a reference.
- Feeds on later steps wait for the workflow. A feed attached to a step only runs when the entry reaches that step. If the entry is parked at an Approval or User Input step, nothing after it runs: no feed, no notification, no integration. Check the entry's current step before you assume a feed failed.
- Entries created through the REST API can skip the workflow start.
POST /gf/v2/entriessaves an entry without the normal submission process, so the feeds and workflow start that hang offgform_after_submissiondon't run. When you need the full pipeline, submit through the form, the/gf/v2/forms/{id}/submissionsendpoint, orGFAPI::submit_form(). - Rerun steps with admin actions, not new test entries. After fixing a step's settings, open an existing entry and use the workflow admin actions (Restart workflow, Send to step). It's faster than refilling the form, and you test against real data.
- Approval steps have two outcomes. Approve or reject. Real processes need more: request changes, escalate, send back to the applicant. Chained approvals and User Input steps can do it, but they get hard to follow past three or four outcomes. How are you handling this? (Disclosure: we built Multi Path Step for this problem.)
- Turn on Gravity Flow's own log. Gravity Flow has its own entry under Forms → Settings → Logging, separate from Gravity Forms. Its log shows step processing in detail, which is usually where the answer is.
<p>Most of the "Gravity Flow is broken" problems we've chased turned out to be one of these. Add yours in the replies and we'll keep this thread as a reference.</p><ol><li><strong>Feeds on later steps wait for the workflow.</strong> A feed attached to a step only runs when the entry reaches that step. If the entry is parked at an Approval or User Input step, nothing after it runs: no feed, no notification, no integration. Check the entry's current step before you assume a feed failed.</li><li><strong>Entries created through the REST API can skip the workflow start.</strong> <code>POST /gf/v2/entries</code> saves an entry without the normal submission process, so the feeds and workflow start that hang off <code>gform_after_submission</code> don't run. When you need the full pipeline, submit through the form, the <code>/gf/v2/forms/{id}/submissions</code> endpoint, or <code>GFAPI::submit_form()</code>.</li><li><strong>Rerun steps with admin actions, not new test entries.</strong> After fixing a step's settings, open an existing entry and use the workflow admin actions (Restart workflow, Send to step). It's faster than refilling the form, and you test against real data.</li><li><strong>Approval steps have two outcomes.</strong> Approve or reject. Real processes need more: request changes, escalate, send back to the applicant. Chained approvals and User Input steps can do it, but they get hard to follow past three or four outcomes. <a href="https://brightleafdigital.io/community/gravity-flow-workflows/3932/">How are you handling this?</a> (Disclosure: we built <a href="https://brightleafdigital.io/gravityops-multi-path-step/">Multi Path Step</a> for this problem.)</li><li><strong>Turn on Gravity Flow's own log.</strong> Gravity Flow has its own entry under <em>Forms → Settings → Logging</em>, separate from Gravity Forms. Its log shows step processing in detail, which is usually where the answer is.</li></ol>