> For the complete documentation index, see [llms.txt](https://support.ordereazi.com/central/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.ordereazi.com/central/order-management/projects/project-history.md).

# Project History

When a client asks why their order changed, or a document didn't reach your accounting system, you need to know exactly what happened and who did it. Project History records every significant event on a project in OrderEazi Central, from the moment it's created. It shows who acted, what they did, when, and whether it worked.

### How to see a project's history

1. Open the project.
2. Select the **History** tab.

Each row shows **Created By**, **Created On**, and **Event**, with the newest first. The latest event also appears at the top of the project, under the project number.

### What gets recorded

* **The project itself:** Created, duplicated, completed, cancelled, and changes to its workflow section.
* **Documents:** Quotes, sales orders, invoices, purchase orders, and other documents created, and files uploaded.
* **Lines:** Products added, changed, or removed, including changes to quantity, cost, selling price, markup, margin, supplier, warehouse, and discount.
* **People and details:** Changes to the sales rep, delivery address, end user, and tags.
* **Workflow and requests:** Steps completed, orders approved or declined, custom validation results, and requests made and answered.
* **Integrations:** Payments, shipments, and webhooks (messages OrderEazi sends to other systems when something changes on the project).

Each row shows who did it. For a person, that's their name. For an app or another system, it's that system's name, so you can tell your team's changes from automatic ones.

### Info, warnings, and errors

* **Info:** Normal activity. It has no icon.
* **Warning:** Something to be aware of that didn't stop anything. It has a yellow triangle.
* **Error:** Something failed and may need you to act. It has a red circle.

When a project has an error that hasn't been resolved, the history icon next to its project number in [My Workspace](/central/order-management/my-workspace.md) turns red. You can spot projects that need attention without opening each one.

### How to resend a failed webhook

When OrderEazi can't deliver a webhook to another system, the error row has a **Resend Webhook** option.

1. On the **History** tab, find the error row.
2. Select **Resend Webhook**.
3. Select **Yes, resend**.

When the webhook goes through, the error row changes to an Info row and the resend option disappears. Once the project has no other unresolved errors, its history icon in My Workspace is no longer red.

**Example:** Your accounting system was offline when you approved an order, so the history shows an error for that webhook and the project's history icon turns red. The next morning you open the **History** tab, select **Resend Webhook**, then **Yes, resend**. The row changes to Info, and the icon is no longer red.

### What Project History does not do

You can't edit or delete history rows. History records what happened, but it doesn't undo it: to reverse a change, change the project again, or [reopen a step](/central/order-management/projects/moving-a-project-through-its-workflow.md).

### Related pages

* [Moving a project through its workflow](/central/order-management/projects/moving-a-project-through-its-workflow.md): the steps recorded in history
* [Requests](/central/order-management/projects/requests.md): requests and their answers, also recorded here
* [My Workspace](/central/order-management/my-workspace.md): spot projects with errors