# Frequently Asked Questions

## Does editing an entry run the workflow again?

No. A run starts when its trigger fires. Editing the entry later does not replay the trigger. Start a new manual run or use another trigger when you need to process the entry again.

![The Flowcrafter workflow dashboard used to manage workflows](/documentation/flowcrafter/screenshots/admin-workflow-list.png)

## What happens if I edit a workflow during a run?

The current run keeps using its **workflow snapshot** (the frozen copy saved when the run began). New runs use the newly saved workflow. You can edit or rename nodes without changing work already in progress.

A node opened from run history shows read-only settings from that run, along with the real input and output.

![A saved run's Send Email settings and actual output](/documentation/flowcrafter/screenshots/editor-run-node-output.png)

## Do entry nodes use the original submission values?

Entry-aware nodes use upstream data to identify the entry, then reload that entry from Gravity Forms when the node runs. A [Condition (entry)](/documentation/flowcrafter/nodes/logic/condition-entry/), notification, feed, or entry action therefore sees changes made after an earlier node or [Delay](/documentation/flowcrafter/nodes/flow/delay/).

## What happens if the original entry is deleted?

Entry-aware steps fail if the selected entry cannot be reloaded; they do not use stale field values. Permanent deletion is a separate signal: when Gravity Forms permanently deletes a run's original entry, Flowcrafter cancels its active runs. Moving an entry to Trash does not cancel them.

A run deliberately executing [Delete Entry](/documentation/flowcrafter/nodes/actions/delete-entry/) may continue after its own deletion; other runs for that entry still stop. This uses Gravity Forms' deletion hook, so a direct database deletion that bypasses Gravity Forms does not trigger cancellation.

## Can I run Gravity Forms feeds?

Yes. The **[GF Feed](/documentation/flowcrafter/nodes/actions/gf-feed/)** node runs feeds registered by Gravity Forms add-ons. Put it where the feed should run in the workflow and test its conditions and side effects before activation.

## Why was a node skipped?

Nodes are only skipped when a Condition or [Switch](/documentation/flowcrafter/nodes/logic/switch/) chose another branch. Untaken branches do not execute, and their nodes appear as **skipped**.

## Can an inactive workflow still run?

Automatic form, schedule, and webhook triggers ignore inactive workflows. You can still test the current canvas or start an inactive workflow manually.

## What happens when a payment never completes?

[Wait for Payment](/documentation/flowcrafter/nodes/flow/wait-for-payment/) takes **Overdue** after its configured limit, which defaults to 168 hours. It reloads the entry at the deadline first, so a recently completed payment still takes **Paid**. Clear the limit to wait indefinitely. Taking Overdue does not cancel the payment.

## What happens when nobody responds to an approval?

[Wait for Approval](/documentation/flowcrafter/nodes/flow/wait-for-approval/) takes **Expired** at its configured deadline, which defaults to 72 hours. This applies to approval waits created after expiry scheduling is available; an older already-waiting request may need manual attention.

## Is Flowcrafter free?

Yes, Flowcrafter is and will always be free. Some nodes can be enhanced with our paid products:

- [GP Populate Anything](https://gravitywiz.com/documentation/gravity-forms-populate-anything/) adds advanced filters and related-entry queries to [Get Entries](/documentation/flowcrafter/nodes/actions/get-entries/).
- [GP Advanced Conditional Logic](https://gravitywiz.com/documentation/gravity-forms-advanced-conditional-logic/) adds nested rule groups to [Condition (entry)](/documentation/flowcrafter/nodes/logic/condition-entry/), such as “Pending and either urgent or overdue.”

A premium node can remain visible in the picker even when its product is not installed. Here Get Posts is unavailable until Populate Anything is available; the screenshot does not show an installed query integration.

![A locked Get Posts item identifies the product it needs](/documentation/flowcrafter/screenshots/action-get-posts-locked.png)

## What happens when no Switch case matches?

Switch takes its always-present **Default** branch. Connect Default to the fallback behavior you want for empty or unexpected values.

## Does Filter choose a workflow branch?

No. [Filter](/documentation/flowcrafter/nodes/flow/filter/) checks each item in a list and returns a shorter list through one output. Use Condition or Switch to route one run, or [Split](/documentation/flowcrafter/nodes/flow/split/) to send list buckets down separate branches.

## Related pages

- [Troubleshooting](/documentation/flowcrafter/reference/troubleshooting/)
- [Running & Monitoring Workflows](/documentation/flowcrafter/building/running-and-monitoring/)
- [Pausing & Waiting](/documentation/flowcrafter/building/pausing-workflows/)