How to Use the End Session Node in Workflow Builder

The End Session node creates a session boundary without ending the guest's workflow. FMX saves and closes the current session, starts a clean session, and then continues to the next connected node automatically.

This is useful when one purchase or guest journey should produce several separate Final Photos. For example, you can charge $10 once, let the guest create three photos, and store each photo as its own FMX session. Place two End Session nodes between the three photo sections to do this.

The counting rule: To create N sessions inside one workflow run, use N - 1 End Session nodes. Three sessions need two boundaries; four sessions need three.

The End Session node is supported by both FMX for Windows and FMX for iPadOS.

What Is the Difference Between a Workflow and a Session?

A workflow is the complete path that the guest follows. It can include payment, capture, AI processing, preview, printing, and sharing.

A session is one self-contained set of guest data inside that path. Its Raw Photos, Final Photo, contact details, survey answers, and output records belong to one session ID.

Normally, one complete workflow run is also one session. End Session lets you divide the workflow into several sessions while keeping the guest in the same continuous experience.

When FMX reaches End Session, it:

1. Finalizes the active session and its media.
2. Starts a new session with a new session ID.
3. Clears session-specific photo and guest data for the new section.
4. Continues through the End Session node's outgoing connection.

The node does not display a guest screen and has no settings to configure.

Example: Charge $10 for Three Separate Final Photos

Suppose your offer is $10 for three photo sessions. The guest should pay once, create three Final Photos, and reach the payment step again only after all three are complete.

In this example, $10 Payment means the payment-enabled Selection Screen or payment-triggered step used by your event. Configure that payment experience for $10, then connect its approved path to Photo Session 1.

Build the main path like this:

$10 Payment → Photo Session 1 → End Session → Photo Session 2 → End Session → Photo Session 3 → Workflow completes

Each Photo Session section can contain the steps needed for one finished result:

Take Photo → AI or effects, if used → Save Final Photo → Preview, Print, or Share

The result is:

Point in the workflow	What FMX does
$10 Payment	Charges the guest once before the package begins
Photo Session 1	Creates and saves Final Photo 1 under session ID 1
End Session 1	Finalizes session 1 and starts session 2
Photo Session 2	Creates and saves Final Photo 2 under session ID 2
End Session 2	Finalizes session 2 and starts session 3
Photo Session 3	Creates and saves Final Photo 3 under session ID 3
Workflow completion	Finalizes session 3 and returns the experience to its starting path for the next purchase

The End Session nodes do not send the current guest back to the $10 payment step. They follow their connected outgoing paths to the second and third photo sections. After the third section finishes, the normal workflow loop can return to the start, where the next guest pays for the next package.

Do not add a third End Session after Photo Session 3 unless you intentionally want to start a fourth session. The normal end of the workflow finalizes the last session.

Why the Boundaries Matter

Without End Session, all three capture sections run under one session ID. Multiple captures and Save Final Photo steps remain part of the same guest session instead of becoming three independent session records.

With two End Session boundaries:

• Each section starts with clean session media and photo numbering.
• Each Final Photo belongs to its own session record.
• Session-based queues, galleries, analytics, and output records can distinguish the three results.
• The guest completes one uninterrupted paid experience instead of returning to the start after every photo.
• The payment step runs once for the package rather than once per Final Photo.

This is especially helpful for prepaid packages, themed photo bundles, three-look AI experiences, and any offer where one payment includes several separate deliverables.

Add End Session in Workflow Builder

1. Open the event's workflow in Foto Master Cloud → Workflow Builder.
2. Build the payment path and the first complete photo section.
3. Select Add Step, open Feature, and add End Session.
4. Connect the last step of Photo Session 1 to the first End Session node.
5. Connect that End Session node to the first step of Photo Session 2.
6. Build Photo Session 2 through Save Final Photo and any output steps that belong to that photo.
7. Add a second End Session node and connect it to Photo Session 3.
8. Build Photo Session 3 through its final output and let that path complete normally.
9. Save the workflow and make sure it is assigned to the intended experience.
10. Sync the event in FMX for Windows or FMX for iPadOS before testing.

End Session has no configuration panel. Its position and connections define its behavior.

Where to Place Preview, Print, and Sharing Steps

Place every step that needs the current Final Photo before the End Session boundary for that section.

For example:

Take Photo → Save Final Photo → Preview → Print Copies → End Session

The new session begins with clean session-specific media. If you place a print, email, SMS, QR, or other current-photo output after End Session, it belongs to the new session and cannot be expected to use the previous section's Final Photo.

If you want to present one combined sharing screen only after all three photos, first test that design with your exact delivery method. The safest standard workflow is to complete each photo's required output before its End Session node.

Connect Every Boundary Deliberately

An End Session node in the middle of a workflow needs an outgoing connection to the next photo section. FMX follows that connection after creating the fresh session.

If a top-level End Session has no outgoing connection, FMX treats that branch as complete and returns to the workflow's start. In the $10 example, that could take the guest back to payment too early.

Use a simple left-to-right path when possible, and check that each boundary points to the correct first step of the next section.

Test the Complete Package

Run a production-style test before the event:

1. Start at the payment step and complete one approved $10 test payment.
2. Finish Photo Session 1 and confirm its Final Photo is saved and delivered as intended.
3. Confirm FMX advances into Photo Session 2 without showing payment again.
4. Repeat the check for the second boundary and Photo Session 3.
5. Confirm the three Final Photos appear as three separate sessions.
6. Confirm the workflow returns to its starting path only after Photo Session 3 is complete.
7. Start a new run and verify that payment is requested for the next package.

Test every branch, including retake, AI error, skip-print, payment cancellation, and timeout paths. Each successful path should either reach the correct End Session boundary or finish the package intentionally.

Troubleshooting

The guest reaches payment again after the first photo

The first End Session probably has no valid outgoing connection, or it points back to the workflow start. Connect it directly to the first step of Photo Session 2, save, and sync again.

The three photos appear in one session

Confirm that two End Session nodes are placed between the three Save Final Photo sections. Make sure the workflow path actually passes through both boundaries; a branch may be bypassing one of them.

The second photo uses media from the first photo section

Check that the End Session node is positioned before the next section's first capture or AI step. It should be reached only after all output for the previous photo is complete.

Printing or sharing cannot find the expected photo

Move the affected output step before the End Session node for that photo. Save Final Photo must also run before Preview, Print Copies, email, SMS, or QR sharing.

The package creates too many sessions

Remove unnecessary boundaries at the start of the workflow, next to another End Session node, or after the final section. For a three-session package, the normal path should contain exactly two End Session nodes.

FMX cannot start the next session

If FMX reports that it could not start a new session, stop the experience, confirm the event is still selected, sync the latest workflow, and start again. If the message returns, collect the FMX logs and contact Foto Master Support.

See Key Concepts: Workflows, Steps, Edges, and Triggers, Session Lifecycle in FMX, and Payment Type Selection Screens for the surrounding workflow concepts.