> For the complete documentation index, see [llms.txt](https://help.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.filed.com/reference/clients/client-statuses.md). # Client statuses Each client carries two overlapping status signals: a lifecycle state (Active or Archived) and a processing state derived from the most recent binder creation (Active, Processing, or Failed). Both combine into the Status badge shown in the client list and the client hub header. ## How statuses work Every client has a stored lifecycle status of `active` or `archived`. On top of that, Filed derives a display status from the latest binder creation workflow: * **Lifecycle `archived`**: the badge always shows Archived, regardless of binder creation state. * **Lifecycle `active`**: the badge reflects the binder creation outcome - Active (completed), Processing (running), or Failed. So the Active, Processing, and Failed badges only appear for clients that have not been archived. ## Active A client is Active when their most recent document binder has been successfully created. All product cards in the client hub are available and interactive. This is the normal working state. The Active badge appears in green. ## Processing A client shows Processing while binder creation is running, typically just after a client is created with documents or when new files are added. The badge displays an animated spinner. While a client is Processing, the tools are not yet available: * **Chat** is disabled with the message "Available once documents are processed." * **Binder** shows a Processing badge and is not interactive. * **AI Tax Prep**, **AI Review**, and **AI Tax Planning** require processing to complete before they can run. ## Failed A client shows Failed when the binder creation workflow encountered an error that prevented documents from being fully processed. The Failed badge appears in red. When a client is in the Failed state, the Binder card shows a red "Failed" badge. (The "N Missing" badge is a different signal: it appears when binder creation completes but N expected documents were not found, and clicking it filters the binder to those documents. It does not indicate a workflow failure.) To recover, open the Files panel, re-upload the affected files, and wait for binder creation to run again. If the problem persists, contact support with the client name and the names of the affected files. ## Archived Archiving moves a client off the active list without deleting any data. The client retains all uploaded documents, binder content, task history, and assignees. The Archived badge appears in gray. Archived clients are hidden by default. To view them, turn on the **Archived** toggle in the client list toolbar. To restore one, open its ⋯ menu and select **Unarchive**. Archiving is the right choice when a client's work is complete for the year and you want to keep the record without cluttering the active list. Unlike deletion, archived clients can be restored at any time. ## Deleted Deleting a client permanently removes the client record and all associated data: documents, binder content, task results, and assignees. Deletion is initiated from the ⋯ menu and requires confirmation. The dialog states: "This permanently deletes the client and all of their data. This action cannot be undone." A deleted client cannot be recovered. If there is any chance you will need the data later, archive instead. `Deleted` is maintained as an internal database state but is never shown as a badge in the product. Once a client is deleted, they no longer appear anywhere in Filed. ## Status reference table | Status | Trigger | Badge appearance | Product cards available | Recommended action | | ---------- | -------------------------------------- | ---------------- | -------------------------------------------------- | -------------------------------------------------------------- | | Active | Binder creation completed successfully | Green "Active" | All cards | None: normal working state | | Processing | Binder creation is currently running | Animated spinner | None (Binder and Chat disabled; AI tools disabled) | Wait for binder creation to complete | | Failed | Binder creation encountered an error | Red "Failed" | None (Binder shows a red "Failed" badge) | Re-upload affected files; contact support if issue persists | | Archived | Client was manually archived | Gray "Archived" | Not applicable | Unarchive to resume work, or leave archived for record-keeping | ## Filtering by status The **Status** filter in the client list toolbar lets you show only clients in a given state. Available options are: All statuses, Active, Processing, and Failed. Archived clients are not included in any status filter option. They are hidden from the list entirely until you enable the **Archived** toggle. The Archived toggle and the Status filter work independently: when both are active, you see archived clients filtered to whatever additional criteria you have set. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.filed.com/reference/clients/client-statuses.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.