Check that the workflow is active, the event qualifies, the step is due, and recipient details exist. Review run history before retrying.
Why this matters
A workflow repeats work for the right event at the right time. Rae can prepare a complete draft quickly; your team then checks every starting condition, recipient, message, and task before publishing.
Before you start
Know the event or lead condition that should start the workflow and who should receive each action.
In Releventful
Open the affected event's activity or workflow history and note the starting condition, due time and item status.
In Manage Portal Templates > Edit workflow, open that item and check its trigger, conditions, recipient and Turn this workflow on when published switch.
Correct the missing setting, click Save draft, test with a matching event, then publish after reviewing impact; check history before manually sending a message.
How to make the most of this step
Check the event type, starting condition, item on/off state, due time, and intended recipient. Then confirm the event has the proposal, status, payment, or other information required by that condition. Preview with one event that should qualify and one that should not. Avoid manually sending a duplicate until you have checked event activity.
A useful decision
Start with the event history before creating a replacement task or sending a manual message. The item may be waiting for its trigger, turned off, missing a recipient, or scheduled for a later time.
Check the result
Preview a matching example and monitor the first live run. Confirm any message reached the intended person.
Important to know
A saved draft is not live. New items begin off for review. A published workflow can send real messages or create tasks when its conditions are met; existing events require their own impact review.