Quick answer: Instead of a single reminder, you can make AlisQI send a reminder every few days — automatically repeating until a record's status is Closed. This uses two workflows: one sets an initial reminder date when the record is created, and the other sends the reminder and pushes that same date forward again, creating a self-sustaining loop that only stops once the status changes to Closed.
This is an advanced technique. Make sure you're comfortable with Result Transfer and the basic due date/reminder workflow before building this.
Before you start
- A plain, non-calculated date field — call it for example Reminder date — added to your form.
- Familiarity with Result Transfer.
- Familiarity with the basic due date/reminder workflow (this builds on it).
Step-by-step: building the loop
Step 1: Add the Reminder date field
Add a non-calculated ''date field'' named Reminder date to the form. This field will be updated automatically by the workflows below — you won't need to set it manually.
Step 2: Build the workflow that sets the first reminder
This workflow runs once, when the record is first created, to schedule the first reminder.
- Set the trigger to Entry — this workflow should fire when a new result is entered.
- Add a Result transfer that sets Reminder date automatically, using the function:
DATE_ADD_DAY({datefield}, #ofdays)For example, to remind 7 days before the due date, subtract by using a negative number of days, or add days to schedule it after another date — adjust {datefield} and #ofdays to fit your use case. 
3. This workflow doesn't need a recipient — nobody should be notified by it directly.
4. Use the Subject and Message fields just to describe what the workflow does, for your own future reference.
5. Save the workflow
Step 3: Build the workflow that sends the reminder and repeats it
This is the workflow that actually notifies someone — and that keeps itself going.
- Set the trigger to On date, using the Reminder date field.
- Add a filter so it only fires when Status is not Closed — this is what breaks the loop once the record is done.
- Add a Result transfer that updates Reminder date again, advancing it by another interval.
- Add a Recipient — for example, the Action owner — and a Subject and Message, since this workflow is the one that actually reaches someone.
- Select Save
How the loop works: each time this workflow fires, it pushes Reminder date forward by another interval, which schedules its own next run. The loop only ends once Status reaches ''Closed'' — at that point, the filter in step 2 stops the workflow from firing again, even though Reminder date would otherwise keep advancing.
With this setup, you don't need a separate one-off Due date workflow — the repeating reminder already covers ongoing alerts.
Key terms used in this article
DATE_ADD_DAY({field}, #ofdays)– a calculation function that adds a given number of days to a date field's value; used here to compute the next reminder date.- Non-calculated field – a field whose value is set directly/manually (here, by a Result Transfer) rather than computed live from a formula each time it's viewed.
- Loop-breaking condition – the filter (Status not Closed) that determines when a self-repeating workflow stops firing.