Dubsado Payment Plans and Late Bookings: What Happens When a Client Books Inside Your Timeline

& Flows

11/11/2026

A business owner in the Dubsado community asked a question recently that comes up for anyone with a long booking timeline. Their final payment is due 45 days before the project date, and a client just booked 40 days out. What does Dubsado do with a date that has already passed?

Dubsado payment plans and flows both work out their dates from the date saved on the project, and neither one shifts a date because the client booked late. A flow action whose time has passed pauses the flow. A payment installment whose due date has passed is late from the start. Both are fixed on the project itself, and both can be planned for in your setup.

What Dubsado does with a date that has already passed

Dubsado 3.0 calls workflows “flows.” When you set a flow action to run a number of days before the project start date, Dubsado calculates the send date from the date on the project. If that send date is already behind you when the flow reaches the action, the action does not run. It shows this error instead: “The trigger for this action has expired. Please select a new trigger or force now.”

The flow then pauses, and no further actions run until you deal with the error. So a late booking costs more than one missed email. Every action after the expired one waits too, including steps that would have gone out on time, such as a questionnaire you send 30 days before the date.

Payment plans work from the same project date. An installment set to 45 days before project start gets a due date 45 days before the project start, even when that day has already passed. On a booking 40 days out, the final payment comes due five days before the client booked. Dubsado uses the payment plan to recognize when a payment is late, so that installment is late before the client has signed anything.

If a client opens an invoice and sees a payment past due before they have signed the contract, check the installment due dates first, starting with any that are timed off the project date.

How to fix a late booking that is already in Dubsado

Find the flow that paused

Open Flows in the sidebar and choose the Errored view. It lists every flow with an error across all your projects. Open the one for the late booking. The expired action has a red error banner on it in the flow builder.

Choose what each expired action should do

Each expired action gets one of three fixes:

  • Force now (the lightning bolt) runs the action right away. Use it for anything the client still needs, like a welcome email or a planning questionnaire. Force now also ignores your active hours, so it sends the moment you click it.
  • Edit the trigger to a time that is still ahead, then click Retry. Use this when the step should still happen later, just not on the original schedule.
  • Skip and mark complete marks the action done without running it. Use it for anything you already handled on the call, or anything that no longer makes sense this close to the date. A skip can’t be undone. To run that step later, you add it back in the flow editor.

Any change you make to the flow here stays on this project. Your flow template does not change.

Resume the flow

Once the error is cleared, check the Paused view. If the flow is still listed there, open it and click Resume. Until you do, the rest of the flow stays stopped.

Fix the payment plan on the invoice

Open the project’s invoice, go to the Payment plan tab and click Edit. Change the installment that is already due to a fixed date you and the client agree on, or make it relative to the contract being signed. Click Update plan to save it. Your payment plan template stays as it is, so the next booking on a normal timeline still gets the 45-day final payment.

How to set up Dubsado payment plans and flows for rush bookings

Time the first payment off the signed contract

Payment plan installments can be relative to the contract being signed as well as to the project date. A retainer set to a few days after contract signed can’t come due before the client signs, however close the project date is. Until the contract is signed, the invoice shows the trigger itself in place of a date. Keep the project date for the later payments, where the timing really depends on the event.

Know your longest lead time

Look through your flow and your payment plan and find the step timed furthest before the project date. For the business owner in the community, that is the final payment at 45 days. Any booking with a project date closer than that will have at least one date that has already passed. When one of those bookings comes in, open its flow the same day, clear the expired actions and check the invoice due dates before the client opens the invoice.

Start rush bookings with Add and edit when you apply the flow yourself

If you start the flow by hand from a project’s Flows tab, choose Add and edit instead of Start flow. Dubsado adds the flow paused, so you can change the triggers for this booking before anything runs. When the timing is right, open the flow and click Resume.

Flows that start from a lead capture form or a public proposal begin running on their own, so for those, the same-day check on any booking inside your longest lead time is how you catch the expired steps.

Plan for late bookings when you map a flow

Late bookings are easier to handle when the flow was mapped before it was built. Mapping it first, as in How to Map a Dubsado Workflow Before You Build It, lets you spot a 45-day step and decide ahead of time what a booking at 40 days should get. If a flow keeps stopping for other reasons, why Dubsado workflows stall covers the other common causes. For every trigger type with a worked example, see Dubsado workflow triggers, mapped step by step on caitpotter.com.

The Forms & Flows Dubsado workflow templates are mapped by industry from inquiry to delivery, and you can see every workflow, form and email in a kit before you buy. If you would rather start from your own process, Dubsado Alchemy turns a guided intake into a build-ready Dubsado workflow map, and your first map is free.

Dubsado payment plans and late bookings: FAQ

Will Dubsado send an expired action later on its own?

No. An expired action keeps its error until you force it, edit its trigger and retry, or skip it. The flow stays paused until then.

Does editing the flow on one project change my template?

No. Changes you make to a flow on a project stay on that project. To change what future bookings get, edit the flow template.

What if the project date is not set yet?

Flow actions timed off the project date wait until a date is added. Payment installments timed off it show the trigger, such as “3 days before project start,” in place of a date.

Does Force now wait for my active hours?

No. Force now runs the action immediately, even outside your active hours.

Keep reading

All posts →

Learn to customize Dubsado proposals with CSS, so your forms support a more intentional, brand-forward client experience. No coding background required.


Stop settling for default Dubsado forms.

Access now