Appendix G — Status reference
Every record in Operentra that moves through a workflow carries a status. This appendix lists, for each of those records, every status the product stores, the English label the screens show for it, what it means, and the action or scheduled job that puts a record into it. A "Flow" line after each table shows the normal path, then the side exits.
Read the tables this way:
- Status (as shown) is the English label on the screen. Where the admin screens and the employee portal word it differently, both are given. "(shown raw)" means no screen has a label for it, so the stored value appears as-is.
- Value is what the database stores. You see it in exports and in the public API.
- Reached by names who or what sets the status. "Automatic" means no one clicks anything: the system sets it as a consequence of another action, or a scheduled job sets it.
Statuses that nothing in Operentra sets are left out.
Status flows by record
Employee
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| New (Pending Activation) (portal: New) | new | The record exists, but the person is kept out of payroll, attendance, leave accrual and headcount. | Every new employee starts here, whether HR adds them or recruitment converts a candidate. A rehired former employee returns here too. |
| Active | active | The person is a working employee. | Activation, which happens when the employee accepts their contract in the portal, when HR uploads a signed copy of the contract, when HR picks Active on the profile Status control of a New employee, or when HR uses bulk activation on the Employees list. Activation also opens the pro-rata leave balance. HR can also set Active on the Status control from On Leave or Suspended, and from Terminated, Resigned or Retired (which also clears the separation date). |
| On Leave | on_leave | HR has marked the person as away. | HR picks it on the Status control of an Active or Suspended employee. Approving a leave application does not set this. Approval writes On Leave into the daily attendance days, not into the employee status. |
| Suspended | suspended | Temporarily suspended. | HR picks it on the Status control of an Active or On Leave employee. |
| Terminated | terminated | Employment ended by the company. | Nothing sets it any more. Only older records carry it, set by hand when the Status control still offered it. |
| Resigned | resigned | The employee left of their own accord. | As Terminated. |
| Retired | retired | The employee retired. | As Terminated. |
| Separated | separated | Offboarding is finished and the final settlement is done. | Automatic: set when HR clicks Complete Settlement on the offboarding record. Final: the Status control offers no status from it, only Rehire. |
Flow: New (Pending Activation) → Active → Separated (through offboarding and Complete Settlement), and Separated → New (Pending Activation) only through Rehire, which starts a new employment on the same record with a new joining date and keeps the earlier one. Side moves, made by HR on the Status control: Active ↔ On Leave, Active ↔ Suspended, On Leave ↔ Suspended. An older Terminated, Resigned or Retired record can go back to Active or be offboarded. No status pick returns to New, and no leaving status can be picked by hand: the Status control offers Start offboarding instead. Editing the employee never changes the status, and the public API cannot set it.
Note: starting an offboarding separation does not change the employee status. The status changes only when Complete Settlement runs.
Pausing someone's pay for a month (Chapter 55) does not change the status either: the person stays Active and is left out of that month's payroll run only.
Contract
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Draft | draft | The contract has been drawn up but is not in force. | HR creates a contract. |
| Active | active | The contract is in force. | HR activates a Draft contract (this also issues the appointment letter automatically). Renewing a contract also creates a new contract that starts directly as Active. |
| Expired | expired | The term has ended. | Automatic: an hourly job (minute 50) expires an Active contract once its end date is before today in the company's own time zone. A company with no time zone set is skipped. Complete Settlement also sets Expired when the separation type is End of Contract. |
| Terminated | terminated | The contract was ended early. | HR terminates an Active contract. Complete Settlement also sets Terminated for any separation type other than End of Contract. The hourly job applies the same rule to employees who were settled before this rule existed. |
| Renewed | renewed | The contract was replaced by a renewal. | HR renews an Active or Expired contract. The old contract becomes Renewed and a new Active contract is created. |
Flow: Draft → Active → Expired or Renewed. Side exit: Active → Terminated.
Note: when the employee accepts the contract in the portal, or HR uploads a signed copy, the contract's status does not change. Either action activates the employee.
Agreement
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Draft | draft | Written, not yet sent. Only HR sees it, and it can be deleted. | HR issues an agreement with Save as draft, or renews one. |
| Waiting for an answer | sent | With the person. Its text is fixed from this moment. | HR issues with Send now, or presses Send on a draft. |
| In force | accepted | The person accepted it. | The person reads it to the end in the portal and types their name. |
| Declined | declined | The person refused it and gave a reason. | The person presses Decline in the portal. |
| Withdrawn | cancelled | Taken back before it was accepted. Its QR code no longer verifies and it has no PDF. | HR presses Withdraw on one that is waiting or was declined, with a reason. Automatic: the daily job withdraws one still waiting for an answer once its expiry date is before today. |
| Ended | ended | Ended early after it was in force. | HR presses End agreement on one that is in force, with a reason. |
| Expired | expired | Its expiry date has passed. | Automatic: a daily job in the workspace's 09:00 hour expires an agreement in force once its expiry date is before today. |
Flow: Draft → Waiting for an answer → In force → Expired or Ended. Side exits: Waiting for an answer → Declined or Withdrawn; Declined → Withdrawn. An agreement in force, expired or ended can be renewed, which writes a new Draft (Chapter 31A).
Note: accepting an agreement changes nothing but the agreement. It does not activate the employee and does not touch their contract.
Approval request
A request that travels an approval flow (Chapter 14A) has one of these beside its own record. The leave application, claim, swap or timesheet keeps its own status, and its module applies the outcome when the request completes.
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Pending | pending | Waiting at its current step. | The request is made (a leave application, an expense claim, an allocation request, an accepted swap or a submitted timesheet) where its flow has someone to decide. |
| Approved | approved | Every step is complete; the module applies the request. | The approvers of the last step approve, in the Approvals inbox or on the module's own page, or the last step's waiting time runs out with Approve automatically. |
| Rejected | rejected | Refused at a step; the module applies the refusal. | An approver of any step rejects it. |
| Cancelled | cancelled | Stopped where it was, with no outcome. | Automatic: the requester withdraws the request (a submitted timesheet, say), or the request was decided outside its flow. |
Flow: Pending → Approved or Rejected. Side exit: Pending → Cancelled. A skipped step, or a waiting time that runs out with Skip to the next step, moves the request on and keeps it Pending; Notify leaves it where it is.
Leave application
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Pending | pending | Waiting for a decision. | The employee applies for leave. |
| Approved | approved | Leave granted. The balance is used, and every day in the range is written into attendance as On Leave. | An approver with leave approval rights approves the application. The approver must be in scope for the employee and cannot approve their own request. |
| Rejected | rejected | Leave refused, with a reason. | An approver rejects a Pending application. |
| Cancelled | cancelled | Withdrawn by the employee. | The employee cancels their own application. They can cancel a Pending application at any time, or an Approved one only if it has not started yet. Cancelling an Approved application gives the days back to the balance and resets those attendance days to Not Marked. |
Flow: Pending → Approved. Side exits: Pending → Rejected. Pending or Approved (not yet started) → Cancelled.
Leave allocation request
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Pending | pending | Waiting on its approval flow (subject leave_allocation; the default is the reporting manager, if their role holds Approve Leave, then Allocate Leave). | The employee asks from My Leaves. |
| Approved | approved | The days were added to the employee's allocation for the current fiscal year. | The flow concludes with approval, from Allocation Requests or the Approvals inbox. |
| Rejected | rejected | Refused, with a reason. | An approver rejects. |
| Cancelled | cancelled | Withdrawn by the employee. | The employee withdraws a Pending request. |
Attendance regularisation and overtime request
Both request types use the same three statuses and the same labels.
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Pending | pending | Waiting for a decision. | The employee submits a regularisation (a corrected status or corrected times for one day) or an overtime request. Only one Pending request is allowed per employee per day. |
| Approved | approved | Accepted. | An approver approves it. The approver must be in scope and cannot decide their own request. An approved regularisation overwrites that day's attendance with the requested status and times, and records what the day showed before. Overtime only: if Attendance Settings require overtime approval and auto-approve is on, the request is created already Approved, with no approver recorded. |
| Rejected | rejected | Refused. | An approver rejects it. |
Flow: Pending → Approved. Side exit: Pending → Rejected. Neither request type can be cancelled.
Roster entry
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Draft (dashed chip) | draft | Planned, not yet what anyone reads. | The nightly pattern expansion, a cell edit on the week grid, Copy previous week, or Unpublish. |
| Published (solid chip) | published | Final: attendance, reminders, payroll and the portal read it. | Publish on the week grid, or an approved swap, which writes both days published with source swap. |
Flow: Draft → Published. Side exit: Published → Draft (Unpublish). Clear entry removes the row so the pattern, assignment or default shift decides again; the roster.entry.changed webhook then carries removed.
Shift swap or drop
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Waiting for colleague | pending_counterpart | Offered; the named colleague (swap) or anyone with the day off (drop) has not answered. | The employee presses Swap or Drop on a published future day of theirs. |
| Awaiting approval | pending_approval | The colleague accepted or took the drop, and the request waits for a decision: on its approval flow (an approval instance of subject roster_swap is open), or, in a workspace with no flow for swaps, for someone who can publish the roster. | The colleague accepts. Nothing is applied until someone decides. |
| Approved | approved | Both days rewritten. | The flow concludes with a yes, in the Approvals inbox or on the roster's Swaps & drops tab; with no flow, a planner approves on that tab. |
| Rejected | rejected | Refused; the roster is as it was. | The flow concludes with a no, a planner rejects on the Swaps & drops tab, or the named colleague declines the swap. |
| Cancelled | cancelled | Withdrawn. | The requester cancels while the request is waiting. |
| Expired | expired | Its day passed before it was accepted or approved; the roster is as it was, and its approval left the inbox. | Automatic, within the hour, once a day of the request is over on the clock of the person who works it; or at once when someone tries to accept or approve it after that. |
Flow: Waiting for colleague → Awaiting approval → Approved. Side exits: Waiting for colleague or Awaiting approval → Cancelled, or → Expired; Awaiting approval → Rejected; Waiting for colleague → Rejected (the colleague declines). One request can be open per employee per day.
Timesheet
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Draft | draft | Being filled in; not yet sent for approval. | Saving the week on My Timesheet. A submitted week the person withdraws, and a returned week they edit, come back here. |
| Submitted | submitted | Waiting for approval; the person can withdraw it but not change it. | Submit for approval on My Timesheet, which needs at least one entry. An approval request of subject Timesheet opens. |
| Approved | approved | Final: the week counts as the person's hours, and nothing reopens it. | The flow concludes with a yes, in the Approvals inbox, on Team Timesheets or on Timesheets › Review. |
| Returned | rejected | Sent back with the approver's note. | Return for changes. |
Flow: Draft → Submitted → Approved. Side exits: Submitted → Draft (Withdraw); Submitted → Returned, then → Submitted again as it is, or → Draft once edited. A project reads Active or Archived (an archived project takes no new hours), and a project's task Open or Done (Chapter 43A).
Attendance day statuses (Daily Attendance)
Daily Attendance shows two kinds of day. Stored days have a saved attendance record. Synthesized days have no record, so the screen works out a status from the calendar. Synthesized statuses are never saved. If a stored day also falls on a holiday or a weekly off-day, the screen adds a small Holiday or Weekend tag beside the main status.
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Present | present | Worked, on time. | Stored. Set when the employee clocks in within the grace period (portal, geo or biometric punch). Also set by the daily auto-present job, which runs at 00:30 company time and marks the previous day for staff on an Auto-Present shift; by HR marking the day; by the bulk upload; and by an approved regularisation. A clock-out that arrives with no clock-in also creates a Present day. |
| Late | late | Clocked in after the grace period. | Stored. Set automatically from the clock-in time (first late threshold), or by HR marking, the bulk upload or a regularisation. |
| Early Leave | early_leave | Left before the shift ended, beyond the grace period. | Stored. Set when the clock-out time is graded: when HR marks the day with times, when biometric punches are merged, when a shift change re-grades past days, or through the bulk upload or a regularisation. A clock-out from the portal or a geo punch records the early minutes but does not change the status. |
| Half Day | half_day | Counted as half a day. | Stored. Set automatically when lateness or early leaving passes a threshold whose action is Half Day, or by HR marking, the bulk upload or a regularisation. |
| Absent | absent | Did not work. | Stored: a threshold whose action is Absent, HR marking, the bulk upload or a regularisation. Synthesized: any past working day with no record, no approved leave and no exempt shift. |
| On Leave | on_leave | On approved leave. | Stored: written for every day of a leave application when it is approved. Synthesized: a day with no record that falls inside an approved leave. |
| Holiday | holiday | A public or company holiday. | Stored: the auto-present job (Auto-Present shifts) or HR marking. Synthesized: a day with no record that is a holiday. |
| Weekend | weekend | The employee's weekly off-day. | Stored: the auto-present job (Auto-Present shifts) or HR marking. Synthesized: a day with no record that is a weekly off-day, or the substitute rest day of a rest-day swap. |
| WFH | work_from_home | Worked from home. | Stored only: HR marking, the bulk upload or a regularisation. |
| Comp Off | compensatory_off | Compensatory day off. | Stored only: HR marking, the bulk upload or a regularisation. |
| Not Marked (portal: Pending) | not_marked | No attendance yet. | Synthesized: today, with no record yet. Stored: the days of an approved leave revert to Not Marked when the leave is cancelled. HR can also mark a day Not Marked. |
| Upcoming | upcoming | A future day. | Synthesized only: any day after today. |
| Exempt | exempt | No punch required. The day counts as worked. | Synthesized only: a working day with no record for an employee whose shift uses the Punch Not Required mode. |
A punch's source names how it arrived: manual (HR), auto (the auto-present job), regularization, biometric, geo (the phone), api, kiosk (a tablet at the door, with the device named) and offline_replay (a GPS punch saved on the phone with no signal and sent later, recorded at the time it was pressed; only where the workspace accepts offline punches, Chapter 41). A day the workspace closed itself carries the remark auto_checkout (Chapter 36); the day's status is whatever a punch at the shift end would have given it, and the remark comes off if the person's own clock-out arrives later and replaces the system's.
When the calendar decides a synthesized status, the first rule that applies wins: Holiday, then Weekend, then On Leave, then Exempt, then Absent (a past day), then Not Marked (today), then Upcoming (a future day).
Flow (a normal working day): Upcoming → Not Marked (today) → Present or Late at clock-in → possibly Early Leave or Half Day when the day is graded → Absent if the day passes with no record.
When the day is graded, the most severe status wins: Absent, then Half Day, then Late or Early Leave, then Present. Punches never overwrite On Leave, Holiday, Weekend, WFH or Comp Off, and never overwrite a day HR has locked with Force.
Payroll run
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Review (portal: Under Review) | review | Calculated and open for checking. It can be reprocessed. | HR clicks Process Payroll for a month. Reprocessing a Review run keeps it in Review. |
| Approved | approved | Signed off. Nothing is committed yet. | HR approves a Review run. Approval is refused while the pre-flight check finds a blocker. |
| Locked | locked | Closed. Entries are final, bonuses and adjustments are marked paid, loan instalments are settled, and expense claims become Paid. | HR clicks Lock on an Approved run. A run is also locked automatically when HR records any payment on it while it is Approved. Runs created by the salary-history CSV import start as Locked. |
| Disbursed | disbursed | Salaries have been paid out. | HR clicks Mark as Paid for the whole run, which pays every entry not paid yet and not on hold (this sends the acknowledgment-request emails), or Finalize Run when every entry is paid or on hold (this sends no emails). Both work on an Approved or Locked run; an Approved run is locked first. Mark as Paid shows again on a Disbursed run while a salary released from hold is unpaid, and pays only that. |
Flow: Review → Approved → Locked → Disbursed. Side move: Approved → Review (Send back to review). A Locked or Disbursed run can no longer be reprocessed.
Salary slip acknowledgment
The slip has no status field of its own. What the screens show comes from two dates on the payroll entry, when it was paid and when the employee acknowledged it, and from whether HR has put the salary on hold (Chapter 58).
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| On hold (portal: On hold; the slip reads Salary on hold) | hold set, no paid date | Earned, but HR is withholding the payment. The figures stay in the run; the bank file, Mark as Paid for the run, marking the entry paid and cheques all leave it unpaid. HR's reason is not shown in the portal. | HR clicks the hold (hand) icon on an unpaid row of a run in review or later, with a reason. Release the hold returns it to Unpaid. |
| Unpaid (portal: Awaiting payment) | no paid date | The salary has not been recorded as paid. | The initial state after processing. Also reached again when HR uses Clear payment on the entry, or when the cheque that paid it bounces or is cancelled. Either way, any acknowledgment already given is cleared too. |
| Awaiting Ack (portal: Action Needed) | paid date set, no acknowledgment date | Paid, and waiting for the employee to confirm receipt. | HR records payment: Mark as Paid for the run, payment for a single entry, or issuing a cheque from the Cheque Register. The acknowledgment-request email goes out unless HR turns emails off. A daily job, shortly after 09:00 in the workspace's time zone, sends at most two reminders, about 2 days and 5 days after the first email. |
| Acknowledged | acknowledgment date set | The employee confirmed receipt. | The employee clicks Acknowledge Receipt in the portal. The time and IP address are recorded, and the signed PDF slip is emailed to them. |
Flow: Unpaid → Awaiting Ack → Acknowledged. Side moves: back to Unpaid through Clear payment or a bounced or cancelled cheque; Unpaid → On hold, and back to Unpaid with Release the hold.
The entry also stores calculated (after processing) and finalized (after lock or payment), but no screen shows those values.
Salary record
An employee's salary records are listed with their status in the salary history under Assign Salary and Change Structure (Chapter 52). A record has no status field: the status is worked out from its dates.
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Scheduled | scheduled | Starts on a later date. | HR records a salary, an increment or a bulk salary row with a future effective date. |
| In force | in_force | The salary that applies today. | Its effective date has come and it has not ended. |
| Ended | ended | Its last day has passed. | A later salary record starts, and this one is closed on the day before it. |
| Replaced | replaced | Never applies. Kept only because a payroll run was built on it. | HR records a salary dated on or before this record's start. A replaced record that no payroll run used is removed instead. |
Flow: Scheduled → In force → Ended. Side move: a record becomes Replaced when a salary is recorded from a date on or before its start. A record entered by mistake can be deleted from the history, within the limits in Chapter 52.
Loan and loan instalment
Loan
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Pending | pending | Waiting for a decision. | The employee applies in the portal. Loans are not available to employees whose loan eligibility is switched off. |
| Active | active | Being repaid through payroll. | An approver approves a Pending loan. The approver cannot approve their own loan. |
| Paused | paused | Repayment stopped. | HR clicks Pause on an Active loan's page. Its Upcoming instalments that no processed run has claimed become Skipped. |
| Completed | completed | Fully repaid. | Automatic: set when a payroll lock settles the last instalment. Resume also completes a loan that has nothing left to collect. |
| Rejected | rejected | Refused, with a reason. | An approver rejects a Pending loan. |
Flow: Pending → Active → Completed. Side exits: Pending → Rejected. Active → Paused, and back to Active with Resume.
Loan instalment
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Upcoming | upcoming | Not yet recovered. | Every instalment is created as Upcoming when the loan is applied for. An instalment also returns to Upcoming when the run that claimed it is reprocessed, and when HR resumes a paused loan: an instalment whose month passed while the loan was paused moves to the end of the schedule, and the instalments are renumbered. |
| Paid | paid | Recovered through payroll. | Automatic: payroll processing claims the instalments of Active loans whose month is now or earlier, and locking the run marks them Paid. An instalment claimed before the loan was paused is still marked Paid when its run is locked. |
| Skipped | skipped | Not recovered while the loan is paused. | Automatic: set when HR pauses the loan, on Upcoming instalments that no processed run has claimed. |
Flow: Upcoming → Paid. Side move: Upcoming → Skipped when the loan is paused, and back to Upcoming when it is resumed.
Recurring deduction
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Active | active | Taken by each payroll run its dates cover, in priority order. | New Deduction on Payroll › Recurring Deductions, or Resume on a paused one. |
| Paused | paused | Skipped by every run until resumed; nothing is owed for the months skipped. | Pause. |
| Completed | completed | Its cap is reached. Final. | Automatic: locking (or paying) the run that takes the last sum under the cap. |
| Cancelled | cancelled | Ended from the next run; what earlier runs withheld stays. Final. | Cancel. |
Flow: Active → Completed. Side moves: Active ↔ Paused; Active or Paused → Cancelled. A completed or cancelled deduction can no longer be edited. Each month's take is claimed when the run is processed and paid when the run locks; reprocessing the run first releases the claim (Chapter 60A).
Expense claim
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Draft | draft | Being prepared. Only the employee sees it. | The employee saves a claim without submitting it. Only Draft claims can be edited. |
| Awaiting Manager | submitted | Waiting for the reporting manager. | The employee submits, either when creating the claim or from a Draft. |
| Awaiting HR | manager_approved | The manager approved it. Waiting for HR. | The employee's reporting manager approves it. |
| Approved | approved | HR approved it, and the reimbursement is queued as a non-taxable payroll addition in the first open payroll month. | HR approves it, from Awaiting Manager (HR override) or from Awaiting HR, and something is owed to the employee. |
| Paid | paid | Reimbursed through payroll. | Automatic: set when the run that paid the reimbursement is locked, marked as paid or finalized. |
| Closed | closed | HR approved it and nothing was owed, because every item was paid on the company card. No payroll addition exists, so no run ever marks it Paid. | HR approves a claim whose reimbursable amount is zero. |
| Rejected | rejected | Refused, with a reason. | The reporting manager rejects it while it is Awaiting Manager, or HR rejects it while it is Awaiting Manager or Awaiting HR. |
| Cancelled | cancelled | Withdrawn by the employee. | The employee cancels their own claim from Draft, Awaiting Manager or Awaiting HR. |
Flow: Draft → Awaiting Manager → Awaiting HR → Approved → Paid. A claim paid entirely on the company card goes from Awaiting HR straight to Closed. Side exits: Awaiting Manager → Approved or Closed (HR skips the manager step). Rejected (from Awaiting Manager or Awaiting HR). Cancelled (before HR approval).
Separation and clearance (offboarding)
Separation (clearance status)
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Pending | pending | No checklist item is done yet. | HR opens a separation. The default checklist is created with it. Only one open separation is allowed per employee. |
| In Progress | in_progress | Some checklist items are done or waived. | Automatic: recalculated every time a checklist item changes or the record is opened. |
| Ready to Settle | completed | Every item is done or waived (the Provident Fund item is not required here). | Automatic: the same recalculation. HR is emailed when it is first reached. |
| Settled | settled | Final settlement is done. The employee becomes Separated, and their Active contract is closed. | HR clicks Complete Settlement on a Ready to Settle separation. Nothing can be edited after this. |
| Cancelled | cancelled | The separation was abandoned. | HR cancels any separation that is not Settled. |
Flow: Pending → In Progress → Ready to Settle → Settled. Side exit: Cancelled (from anything except Settled).
Clearance checklist items
Items have no status label. The screen shows a tick for done, an extra "waived" tag for waived items, and an "auto" tag for items the system checks. Stored values: pending (open), completed (HR clicks Mark done on a manual item; automatic items complete themselves once there are no outstanding assets or loans, or once the Provident Fund option is chosen at settlement; the Provident Fund item is only on the checklist of someone with a provident fund, and an older separation that lists it for someone without one shows it as done), and waived (HR clicks Waive; Reopen sets the item back to pending).
Onboarding pipeline
Pipeline
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Preparing | preparing | Created before the joining date. | Automatic: created with every new employee whose joining date is in the future. |
| Day 1 | day_1 | The joining date has arrived. | Automatic: the starting status when the joining date is today or earlier. A Preparing pipeline becomes Day 1 the first time it is opened, or a task on it is changed, once the joining date has passed. |
| Completed | completed | Every required task is done or waived. | Automatic: set as soon as the last required task is done or waived. HR is emailed. A Completed pipeline cannot be reopened. |
| Cancelled | cancelled | Closed early. | HR cancels the pipeline, or Complete Settlement cancels it when the employee leaves with it still open. |
Flow: Preparing → Day 1 → Completed. Side exit: Cancelled.
A transfer or promotion checklist (opened by an activity plan of that kind when the movement is recorded) uses the same statuses, counted from the transfer or promotion date instead of the joining date; completing one sends no onboarding email.
Onboarding tasks
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Pending | pending | Not done. | Every task starts here. HR's Reopen sets a task back to Pending. |
| Done | completed | Done. | HR marks it done. A system-action task (for example, push to biometric device or send the welcome email) is marked Done when its action succeeds. Automatic checks also mark Done the tasks whose work is already finished elsewhere, such as a salary already assigned or an asset already issued. |
| Waived | waived | Skipped on purpose, with an optional note. | HR waives it. |
| Blocked | blocked | A system action failed. The failure message is kept as the task's note. | Automatic: set when a system-action task's action fails. |
Appraisal cycle and appraisal
Appraisal cycle
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Draft | draft | Set up, but not rolled out. | HR creates a cycle. |
| Active | active | Rolled out. Reviews are under way. | Automatic: set on the first roll-out of a Draft cycle. Probation review cycles are created directly as Active. |
| Closed | closed | Finished. Nothing in it can be edited, reviewed or finalized. | HR closes the cycle. A Closed cycle cannot be reopened. |
Flow: Draft → Active → Closed.
Appraisal (one per employee in a cycle)
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Pending | pending | Waiting for the employee's self review. | Created by the roll-out, or for a probation review, when self review is enabled in Appraisal Settings. |
| Self Review (Draft) | self_in_progress | The employee has saved a draft of their self review. | The employee saves a self-review draft. |
| Awaiting Manager | self_done | Waiting for the reviewer. | The employee submits their self review while manager review is enabled. Created at this status by the roll-out when self review is off but manager review is on. Also set when HR changes the reviewer while the old reviewer's draft was in progress. |
| Manager Review (Draft) | manager_in_progress | The reviewer has saved a draft. | The reviewer saves a draft after the self review has been submitted. |
| Awaiting Finalization | manager_done | The reviews are in. Waiting for HR. | The reviewer submits, at any point before this status (a reviewer's submission closes the self review even if the employee had not finished it). Also reached when the employee submits a self review while manager review is off, and created at this status when both reviews are off. |
| Finalized | finalized | The final rating is calculated and recommendations are recorded. | HR finalizes an appraisal that is Awaiting Finalization, in a cycle that is not Closed. |
Flow: Pending → Self Review (Draft) → Awaiting Manager → Manager Review (Draft) → Awaiting Finalization → Finalized. Phases switched off in Appraisal Settings are skipped.
Goal
| Status | Value | Meaning | Reached by |
|---|---|---|---|
| Active | active | Being worked on; check-ins move current. | Set by the employee, their manager or HR. |
| Completed | completed | Done. A goal a manager or HR set writes its merit ledger line (source Goals) now. A goal the employee set for themselves reads Awaiting confirmation until their manager or HR presses Confirm completion, which writes the line; it then reads Confirmed. | A check-in with "This check-in completes the goal", or Mark complete, on an Active goal. |
| Cancelled | cancelled | Dropped; kept for its history. | Cancel goal. A goal with check-ins is cancelled rather than deleted. |
Flow: Active → Completed or Cancelled; Reopen returns either to Active. A 360° feedback request reads pending, submitted, declined or expired (its link ran out, or feedback was closed before it was answered); an appraisal request pending, approved or declined.
Survey and survey invitation
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Draft | draft | Being written; nobody is invited. Only a draft can be deleted. | New survey. |
| Open | open | Taking answers. A survey with a trigger invites people by itself while open. | Open survey, which invites its audience and emails them. |
| Closed | closed | Nobody can answer any more. Final. An anonymous survey's results become readable, and the record of who answered is erased. | Close survey, or Automatic within the hour after the end of its Closes on day. |
Flow: Draft → Open → Closed.
Each person invited has an invitation:
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Not answered yet | pending | Invited; no answer yet. | Being invited: when the survey opens, when HR adds the person, or by the survey's trigger (an onboarding plan item at day 30 or 90, or a separation). |
| Answered | answered | The person has answered. | Send my answers on My Surveys. |
| (not shown) | closed | The survey was anonymous and has closed: whether this person answered is no longer recorded. | Automatic, for every invitation of an anonymous survey, when it closes. |
Flow: Not answered yet → Answered. An invitation to a survey by name keeps its status when the survey closes (Chapter 81A).
Job opening
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Draft | draft | Being prepared. | HR creates an opening. |
| Open | open | Accepting applications. Only an Open opening can be published on the careers site. | HR sets the status to Open (this records the budget approval). |
| On hold | on_hold | Paused. | HR sets it. Leaving Open takes a published posting off the careers site. |
| Filled | filled | The headcount is reached. | HR sets it. It is also set automatically when converting a hire to an employee brings the number of hires up to the headcount. |
| Cancelled | cancelled | Closed without filling. | HR sets it. |
Flow: Draft → Open → Filled. Side exits: Open → On hold (and back to Open). Cancelled. HR can choose any of the five statuses on the opening's page.
Candidate application stages (recruitment pipeline)
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Applied | applied | New application. | The candidate applies on the careers site, or HR adds the candidate to an opening by hand. Either way the opening must be Open. Applying again does not change the stage. |
| Screening | screening | Being screened. | HR moves the application to the next stage. |
| Interview | interview | In interviews. | HR moves it to the next stage. Scheduling an interview also moves an Applied or Screening application here automatically. |
| Offer | offer | An offer has been made. | Automatic: set when HR extends an offer. The screen does not let HR move an application to Offer any other way. |
| Hired | hired | Hired. | The candidate accepts the offer on the public offer page, or HR converts the candidate to an employee. HR can also move the application to Hired when no offer is waiting for the candidate's answer. |
| Rejected | rejected | Turned down by the company. | HR rejects the application with a reason. The candidate is emailed. |
| Withdrawn | withdrawn | The candidate stepped away. | The candidate declines the offer on the public offer page. |
Flow: Applied → Screening → Interview → Offer → Hired. Side exits: Rejected (HR, at any point). Withdrawn (the candidate declines the offer).
A workspace may rename and reorder these stages and add its own between them (Recruitment › Pipeline settings), and an opening may run on its own copy; the keys above are the built-in ones. Hired, Rejected and Withdrawn are end states reachable from any stage.
Offer
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Sent — awaiting candidate (lists: Sent) | sent | Sent to the candidate, waiting for an answer. | HR extends an offer. Extending it again updates the same offer, keeps the same link, and sets it back to Sent. |
| Accepted | accepted | The candidate accepted. | The candidate clicks Accept on the public offer page before the expiry date. The application moves to Hired. |
| Declined | declined | The candidate declined, with a reason. | The candidate declines on the public offer page. The application moves to Withdrawn, and a declined offer cannot be extended again. |
| Withdrawn | withdrawn | The company withdrew the offer. | Only through the API; no screen offers it. |
Flow: Sent → Accepted. Side exit: Sent → Declined.
HR letter request
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Pending | pending | Waiting for HR. | The employee requests a letter in the portal. |
| Issued | issued | The letter has been issued and linked to the request. | HR issues a letter from the request. The employee is emailed the letter. |
| Rejected | rejected | Refused, with a reason. | HR rejects the request. |
| Cancelled | cancelled | Withdrawn. | The employee cancels their own Pending request. |
Flow: Pending → Issued. Side exits: Pending → Rejected. Pending → Cancelled.
Asset (and asset assignment return outcomes)
Asset
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Available | available | In stock and free to issue. | HR adds an asset, or the asset is returned with the outcome Returned (intact). HR can also set it on the edit form. |
| Issued | issued | With an employee. | HR issues an Available asset to an active employee. The edit form cannot set Issued, and it locks the status while the asset is Issued, so the only way out is a return. |
| Maintenance | maintenance | Out for repair. | The asset is returned with the outcome Returned (damaged), which also sets its condition to Poor unless HR picks a condition. HR can also set it on the edit form. |
| Retired | retired | Out of service. | HR sets it on the edit form. |
| Lost | lost | Missing. | The asset is returned with the outcome Lost / not returned, or HR sets it on the edit form. |
Assignment (one row per issue, shown in the asset's history)
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Active | active | Currently held. | HR issues the asset. |
| Returned | returned | Returned intact. | Return outcome Returned (intact). |
| Damaged | damaged | Returned unusable. | Return outcome Returned (damaged). |
| Lost | lost | Never came back. | Return outcome Lost / not returned. |
Flow: Available → Issued → Available (Returned (intact)). Other ways out of Issued: Maintenance (Returned (damaged)). Lost (Lost / not returned). Retired is set by HR.
Field visit
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| In progress | checked_in | The rep is at the client. | The rep checks in from the portal. |
| Completed | completed | The visit is over. | The rep checks out, which records the duration and the outcome. A visit is also completed automatically when the rep checks in to the next visit and agrees to close the open one. Admin can also close an In progress visit as Completed, and the duration is then left unknown. |
| Cancelled | cancelled | Not a real visit. | Admin cancels it, from In progress or from Completed. |
Flow: In progress → Completed. Side exit: Cancelled.
Each visit also gets a verification result at check-in: Verified (verified, inside a confirmed client pin's radius), Unverified (unverified, the client has no pin or only a provisional one) or Flagged (flagged, outside the radius, or the GPS reading was too inaccurate).
Employee document
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Pending | pending | Waiting for HR review. | The employee uploads a document in the portal while document verification is on (the default). |
| Uploaded | uploaded | On file. No review needed. | The employee uploads a document while document verification is switched off for the company. |
| Verified | verified | HR checked it. | HR verifies the document. The employee is emailed. |
| Rejected | rejected | Not accepted, with a reason. | HR rejects the document, or revokes an earlier verification. The employee is emailed. |
| Missing | none stored | No document of a required type is on file. | Shown only on the Document Compliance matrix. It is calculated when the matrix is built and never stored. |
Flow: Pending → Verified. Side exits: Pending → Rejected. Verified → Rejected (revoke). With verification off: Uploaded.
Knowledge base article
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Draft | draft | Not published; its readers do not see it. | New article. |
| Published | published | Readable by its audience on the portal and through the assistant's search. Edits wait in a working copy until Publish changes, which makes a new version when anything changed. | Publish, from Draft or Archived. |
| Archived | archived | Withdrawn from readers; kept with its versions. | Archive on a published article. |
Flow: Draft → Published → Archived, and Archived → Published. Drafts and archived articles can be deleted; a published one is archived first (Chapter 81B).
Company event and reply
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| (no label) | scheduled | Published to its audience. Shown as Over once its end (or, with no end, its start) has passed; it can then no longer be changed or cancelled. | Publish event. There is no draft. |
| Cancelled | cancelled | Called off. Final. It stays on the list of everyone invited with its reason and takes no more replies. | Cancel event, on an event that is not over. |
Each person invited can give one reply, and change it until the event is over:
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Going | going | The person will be there. | Going on the portal's Events page. |
| Maybe | maybe | The person may be there. | Maybe. |
| Can't go | declined | The person will not be there. They are not told if the event is cancelled, and it is left out of their calendar subscribe link. | Can't go. |
A person who has not replied has no row; HR sees them counted under No reply (Chapter 81C).
Course and enrolment
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Draft | draft | Being written. Employees do not see it, and it cannot be assigned. | Create course. A published course also returns to Draft when its last lesson and last question are removed. |
| Published | published | People can be enrolled on it and take it. It can still be edited. | Publish, from Draft, or Publish again, from Archived. Refused with no lesson and no question, or while more questions are asked in a sitting than the course has. |
| Archived | archived | Withdrawn. Nobody new is enrolled, its assignments are switched off, and people who have not finished can no longer continue. Completions and certificates are kept. | Archive on a published course. |
Flow: Draft → Published → Archived, and Archived → Published. A course can be deleted only while nobody has ever been enrolled on it.
Each person enrolled has one status for their latest round of the course:
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Not started | not_started | Enrolled; no lesson marked done yet. | An assignment enrols the person, the next round of a course that repeats starts, or the person chooses Start this course on an open course. |
| In progress | in_progress | Started and not completed. | The person marks a first lesson as done, or starts the quiz. |
| Completed | completed | Every lesson is done and, where the course has a quiz, a sitting was passed. The date is recorded, with Valid until when the course repeats. | Mark as done on the last lesson of a course with no quiz, or a passed sitting. |
| Overdue | none stored | Not completed and past its due date. | Shown in place of Not started or In progress. It is worked out when the list is read and never stored. |
Flow: Not started → In progress → Completed (Chapter 75B).
Request (HR Desk)
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Awaiting approval | awaiting_approval | Sent, and waiting for a decision. The team cannot work it. | The person sends a request of a type that needs approval. |
| Not approved | rejected | The approval was refused. Nothing more can be written on it. | An approver refuses it, with a reason. |
| Open | open | Waiting in the team's list, with nobody on it. | The person sends the request, or its approval is given. Also when a handler puts a request back in the team's list, and when the person replies on or reopens one nobody has. |
| In progress | in_progress | A handler has it. | Take it, choosing who has it, or a first reply to a request nobody has taken. Also when the person replies on a request that was waiting on them. |
| Waiting on the person | waiting_on_person | The desk has asked the person something. | A handler sets it, usually with a reply. |
| Resolved | resolved | The desk has dealt with it. The person can reopen it for seven days. | A handler sets it, with or without a reply. |
| Closed | closed | Finished. Nothing more can be written on it. | Automatic, seven days after it was resolved. Nobody sets it by hand. |
| Withdrawn | cancelled | The person withdrew it before it was resolved. | Withdraw request in the portal. |
Flow: Open → In progress → Resolved → Closed, with Waiting on the person between replies. A type that needs approval starts at Awaiting approval, and goes to Open when approved or to Not approved when refused. A handler can take a Resolved request back to In progress; the person can reopen it for seven days. Closed, Withdrawn and Not approved are ends (Chapter 81D).
Concern (Speak up)
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Not yet acknowledged | new | Raised, and no handler has acknowledged it. Due within 7 days. | The person raises a concern. |
| Acknowledged | acknowledged | A handler has acknowledged it and it is being looked into. An answer is due within 3 months of the day it was raised. | Acknowledge, or a handler's first reply. Also when a closed concern is reopened. |
| Closed | closed | Answered: the handler said what was found and done. Nothing more can be written on it. | Close with an outcome. |
Flow: Not yet acknowledged → Acknowledged → Closed. A handler can reopen a closed concern (81D.9).
Company document
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Draft | draft | Not shared yet. Only a draft can be deleted. | New document in the company document library. |
| Published | published | Shared with its audience on Portal › Company Documents. Attaching a new file makes a new version and, where the document asks for acknowledgement, emails its audience again. | Publish, which needs a file. |
| Archived | archived | Withdrawn. Final: it can no longer be edited, given a file or published. | Archive, from Draft or Published. |
Flow: Draft → Published → Archived. Side exit: Draft → Archived.
Employee photo (upload waiting for review)
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Waiting for HR approval (portal: "Your new photo is waiting for HR approval.") | pending | An upload the employee made, not yet on the record. | The employee uploads a photo while the workspace's employee photo setting is Employees upload, HR approves. |
| (no label) | approved | The upload became the employee's photo. | HR approves it on Profile Approvals › Photos. The employee is emailed. |
| Not approved (portal: "HR didn't approve your last photo.") | rejected | Refused; the upload is deleted. | HR rejects it, with an optional note. The employee is emailed. |
| (no label) | cancelled | Withdrawn or superseded. | The employee cancels it, or uploads another photo, which replaces it. |
Flow: Waiting → Approved. Side exits: Waiting → Not approved. Waiting → Cancelled. With the setting at Employees upload, no review, uploads go straight onto the record and no row waits.
ID card (Brand Studio)
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Active | active | The current card. It verifies as valid while it is not past its expiry and its holder is a current employee. | HR issues it, from Brand Studio › ID Cards, the directory, the profile, the onboarding task, or by fulfilling a request. |
| Replaced | replaced | Superseded by a newer card; it no longer verifies. | Automatic: HR issues a new card to someone who holds an active one. |
| Revoked | revoked | Cancelled; it no longer verifies. The portal says "cancelled". | HR revokes it with a reason; or automatic, when the final settlement is completed, when the employee record is deleted, or on rehire (a card from the earlier employment). |
Shown alongside, never stored as a status: Expired (active and past its expiry date; it no longer verifies), Expires within 30 days, Outdated (the name, photo, designation or department changed since issue), Not printed (still in the print queue) and Returned (marked as handed back to HR; it still verifies if active).
Flow: Active → Replaced, or Active → Revoked. Both are final.
Visiting card order (Brand Studio)
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| In print queue | none stored (no print or cancel date) | Ordered, not yet printed. | HR orders cards, or fulfils an employee's request. |
| Printed (with the date) | none stored (a print date) | Printed and ready to collect. | HR marks the order as printed. The employee is emailed. |
| Cancelled (with the date) | none stored (a cancel date, with the reason) | Called off before printing; it never prints. | HR cancels it with a reason, on Brand Studio › Visiting Cards; or automatic, when the employee's final settlement is completed or their record is deleted. Nobody is emailed. |
Flow: In print queue → Printed, or In print queue → Cancelled. Both are final.
Brand Studio request
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Pending (portal: "Requested on …") | pending | A request for a replacement ID card or for business cards, waiting for HR. | The employee sends it from My ID Card or My Business Card. HR users who can issue cards are emailed. |
| Fulfilled (portal: Done) | fulfilled | HR issued the card or placed the order. | HR fulfils it on Brand Studio › Requests, or issues a card or orders business cards for that person anywhere else in Brand Studio. |
| Rejected (portal: Declined) | rejected | Refused, with a note. | HR rejects it. The employee is emailed the note. |
| Cancelled (portal: Withdrawn, or Cancelled by HR) | cancelled | Withdrawn, called off with its order, or closed because the employee left. | The employee withdraws their own pending request; or HR cancels the visiting card order that fulfilled it (portal: Cancelled by HR, with the reason); or automatic, for a pending request, when the employee's final settlement is completed or their record is deleted. |
Flow: Pending → Fulfilled. Side exits: Pending → Rejected. Pending → Cancelled. Fulfilled → Cancelled (a visiting card request whose order is cancelled). One request of each kind can be pending per employee.
AI assistant confirm card
Each change the AI assistant prepares waits as a card for the person who asked (Chapter 98).
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Awaiting your confirmation | pending | Prepared; nothing has been submitted. | The assistant prepares it after the server's checks. |
| Confirming… | confirming | Being submitted. | The person presses Confirm within ten minutes. |
| Confirmed | confirmed | Submitted, exactly as from the page. | Automatic, when the request succeeds. |
| Failed | failed | The request was refused when confirmed; the card says why. | Automatic, when the request fails. |
| Cancelled | cancelled | Dropped; nothing was submitted. | The person presses Cancel. |
| Expired | expired | Not confirmed within ten minutes; nothing was submitted. | Automatic, ten minutes after it was prepared. |
Flow: Awaiting your confirmation → Confirming… → Confirmed or Failed. Side exits: Awaiting your confirmation → Cancelled, or → Expired. A card can be confirmed only once.
Subscription (billing)
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Trial | trialing | On the free trial. | The workspace signs up (a 14-day trial). Also: a checkout with an offer code (Stripe holds the trial with the card on file), the operator extending the trial (this also revives an Expired trial), or Stripe reporting the subscription as trialing. |
| Active | active | Paying, and fully usable. | Stripe Checkout completes, Stripe reports active, the operator assigns a plan with manual billing, or an AppSumo licence is activated. |
| Payment overdue | past_due | A payment failed. The workspace stays writable while Stripe retries. | Stripe reports a failed invoice payment, or a subscription status of past due or unpaid. |
| Canceled | canceled | Ended. The workspace is read-only. | Stripe deletes the subscription (for example, at the end of the period after an in-app cancellation, since that cancellation only schedules the end), Stripe reports canceled or incomplete-expired, the operator cancels the Stripe subscription, or an AppSumo licence is refunded or detached. |
| Incomplete | incomplete | Stripe has not completed the subscription. | Stripe reports any other status, such as incomplete or paused. |
| Expired | expired | The trial ran out without a purchase. The workspace is read-only. | Automatic: a daily job at 03:10 server time expires a self-serve trial that has no card on file once its end date has passed. Operator-managed workspaces are skipped. |
Flow: Trial → Active. Side exits: Trial → Expired (and back to Trial if the operator extends it, or to Active on purchase). Active → Payment overdue → Active, or Canceled.
The tenant's Billing page labels all six statuses.
Webhook endpoint and delivery
Endpoint
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Not verified | pending | Created, but not yet proven to receive events. Events are not sent to it. | The tenant adds an endpoint. Changing an endpoint's URL also puts it back here. |
| Active | active | Receiving events. | Send test succeeds. Resume also sets Active (the button is shown only once the endpoint has left Not verified). |
| Switched off | disabled | Not receiving events. | The tenant clicks Pause. Also automatic: set after 20 deliveries in a row fail. |
Flow: Not verified → Active. Side exits: Active → Switched off (Pause or 20 failures), and back to Active with Resume or a successful Send test.
Delivery (one per event per endpoint)
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Queued | pending | Waiting to be sent. | Created for each Active endpoint subscribed to the event. A failed attempt with retries left also returns here, with the next try after 1, 5, 30, 120, 300, 600 and then 1200 minutes. Send again also puts a delivery back here and restarts the attempt count. |
| Sending | dispatching | Claimed by the sender. | Automatic: the delivery worker claims it. A claim held for more than 10 minutes is picked up again. |
| Delivered | succeeded | The receiver answered with a success (2xx) code. | Automatic, on a successful attempt. Delivered rows are later removed by the retention job. Failed rows are kept. |
| Gave up | exhausted | Retries ran out. The row stays visible and can be sent again. | Automatic: set after the 8th failed attempt, or at once if the failure is permanent (the endpoint URL is refused, or its secret cannot be read). |
Flow: Queued → Sending → Delivered. Side path: Sending → Queued (retry) → … → Gave up. Send again returns any delivery that is not Sending to Queued.
Integration connection and its activity
The cards on Settings › Integrations for the chat, calendar and ledger connections (Chapter 95), and the Activity list on each connection's page.
Connection (the card)
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Configured | active | Connected; events are delivered. | Connect & test (webhook) or Connect (sign-in with the provider) succeeds; a later Test connection that succeeds returns a card here. |
| Needs attention | error | The credential no longer works; nothing more is sent until a test succeeds. The credential is kept. | Automatic: three deliveries in a row refused by the other side (a deleted webhook, an archived channel, a withdrawn token). A passing failure (the service was down, rate limiting) does not count. |
| Reconnect needed | disconnected | The provider will no longer renew the access; the connection's settings are kept for a reconnect. | Automatic, when the provider refuses to renew the token and asks for a fresh sign-in (or issued no renewable token). |
| Not configured | — | No connection saved. | The starting state; also Disconnect, which deletes the credential. |
| Available | — | The feature is on, but the operator has not registered this provider's app for the installation, so the card cannot be connected yet. | Only the calendars and ledgers; chat needs no app. |
Flow: Not configured → Configured. Side exits: Configured → Needs attention (three refusals) → Configured (a test succeeds); Configured → Reconnect needed → Configured (reconnect); any → Not configured (Disconnect).
Activity row (a journal or a calendar entry)
| Status (as shown) | Value | Meaning | Reached by |
|---|---|---|---|
| Queued | pending | Waiting to be sent. | The event happened (a run was locked, a leave approved). A passing failure returns here, for up to a day. |
| Sending | running | Claimed by the relay. | Automatic. |
| Sent | done | In the ledger or on the calendar; the row links to it. | Automatic, when the other side accepts it. |
| Removed | removed | The calendar entry was taken off again. | A cancelled leave. |
| Waiting for you | waiting | Cannot go yet: the ledger accounts are not chosen. | A run locked before the accounts were saved; it goes out when they are. |
| Failed | failed | Refused by the other side, or the app's own check stopped it (a currency mismatch, a run that does not balance); the row says why. | Automatic. Try again sends it now, after you fix the cause. |
Flow: Queued → Sending → Sent (or Removed, for a calendar entry later cancelled). Side exits: Queued → Waiting for you → Queued; Sending → Failed → Queued (Try again). A journal that was Sent is never posted twice.