Quick answer
Before enabling an approval timeout, inspect the status the step will receive after expiration and the destination that follows it. Do not assume expiration sends a reminder and leaves the decision pending. Test the no-response path using a fictional entry before applying the setting to live client intake.
Write the business rule first
Ask a plain question: what should happen if the decision maker does nothing? Possible answers include asking a backup reviewer, closing the inquiry, or continuing only after a separate manual check. These are different policies. A deadline on a screen cannot decide which one the business intended.
Record the latest acceptable response time, who owns exceptions, and whether the customer should receive any message when the deadline passes. Avoid promising that a prospect has been accepted merely because a timer elapsed. A workflow can be technically successful while communicating the wrong commitment.
Read the setting for the actual step type
The official expiration guide distinguishes User Input and Approval steps. A User Input step can use an expired status with its own next-step destination. An Approval step can change to approved or rejected after expiration. Do not copy a timeout configuration between those step types and assume the semantics stay the same.
Inspect the current settings in the installed version. Capture the expiration basis, final status, and downstream route. If the requirement is escalation to a person, design a reviewed path that preserves that human decision. Do not use automatic approval as a substitute for escalation just to make an overdue entry leave the inbox.
Separate due time from actual processing time
An entry can pass its nominal deadline before the scheduled workflow processor handles it. Gravity Flow uses WordPress scheduled processing, so timing depends on the site's scheduler. A quiet site, blocked cron request, or failed job can delay a time-based action.
Record the submission time, assignment time, calculated expiration time, and observed transition time in one timezone. Keep the server and business timezone explicit. If the observed transition is late, inspect scheduling evidence before changing the deadline. Making expiration more aggressive does not repair a scheduler that is not running.
Build four disposable cases
Test a reviewer approving before the deadline, rejecting before the deadline, doing nothing until after the deadline, and opening an old notification after the workflow has moved on. Use a mail capture inbox and a sandbox destination for any downstream integration. Each case needs its own entry ID so the history stays interpretable.
For the no-response case, compare the actual status and next step with the written business rule. Check whether a customer email, internal email, webhook, assignment, or CRM update occurs. The right final status with an unintended downstream message is not a passing result.
- Keep the timeout long enough to inspect the staging sequence reliably.
- Do not trigger every scheduled job merely to accelerate one test.
- Confirm the old reviewer cannot accidentally act on a completed step.
- Record every automatic message and downstream write from the timeout case.
Check for a circular route
Draw the next-step destinations for approved, rejected, expired, and ordinary completion where applicable. Follow the no-response path until it reaches a stable end or a person. A path that returns to another timed step can repeatedly send messages even when no reviewer is active.
Pay particular attention to a short timeout followed by a notification and another step that points back. Avoid changing live step order while trying to break the cycle without recording what current entries reference. If an actual loop is sending messages, contain the affected workflow and involve its owner before replaying or cancelling customer work.
Roll out with a named exception owner
After staging passes, record the configuration change, affected forms, and responsible reviewer. Observe the first live timeout rather than waiting for a customer complaint. Compare the result with the same acceptance checklist and keep a path to restore the previous settings.
A useful completion record says which outcome occurred, when it occurred, who was notified, and what remains manual. It does not merely say "expiration enabled." Review response-time reports separately from approval decisions so an automation improvement does not hide inquiries that still require a person.
Illustrative diagnostic example, not customer measurements.When to bring in help
For a workflow that approves work without a reviewer, ask HandL WP to inspect the timeout path. Bring the affected step settings, timestamps, and a redacted entry timeline. Contain automated side effects while the decision path is reviewed.
Related troubleshooting
Test saved progress before a workflow continues.
Helpful references
Step expiration behavior. Troubleshooting workflow issues.