Runs and manual activities
Process runs
Section titled “Process runs”Publishing creates a process run: a snapshot of the process definition, anchored on a due date, with one activity run per activity. The run’s page shows the timeline of activities, their status and who is responsible.
A run is running until all activities have completed, then succeeded. If an automated activity fails after its retries, the run is marked failed; you can requeue the activity once the cause is fixed. Runs can be cancelled, which stops any activities that have not happened yet.
Rescheduling
Section titled “Rescheduling”When the due date moves, reschedule the run. Activities that have not been sent or completed are recalculated from the new anchor; activities that already happened keep their history.
Activity runs
Section titled “Activity runs”Each activity run has a scheduled time and a status. Automated activities (notifications, integrations) are executed by Flowstate at the scheduled time and retried on transient failures. Manual activities wait for a person.
Manual activities
Section titled “Manual activities”At the scheduled time the assignee receives an email describing the activity, with a link to complete it. The link works without signing in and is valid for 30 days. Opening it shows the activity’s instructions and a button to mark it done.
Manual activities also appear under Tasks in the app for the assignee, and a workspace admin can reassign one from the run’s page if the original assignee is unavailable.
Email from Flowstate
Section titled “Email from Flowstate”Transactional email is sent from no-reply@flst.app. Links in email point to flst.app; short links look like https://flst.app/i/<code> and resolve to the right page when opened.