# Project History Project History gives you a complete, real-time record of everything that happens on a project - from creation through to delivery. With event typing and webhook tracking, you can instantly see what's working and what needs attention. ### ๐Ÿงพ **What is Project History?** Project History is an audit trail attached to every project in OrderEazi Central. Each time a significant action occurs - a quote is sent, a document is created, a webhook fires - a history entry is recorded. Every entry captures: * Who performed the action (a user, an app, or an external system) * What happened (the event type and a description) * When it happened * Whether it succeeded or failed This provides you with full visibility into the project lifecycle, eliminating the need to ask your team or check external systems. ### โš™๏ธ **How It Works** #### Event Types Every history entry is classified with a severity level: Info - Normal activity. Things are working as expected. No icon is displayed in the history view. Warning - Something to be aware of, but not blocking. Displayed with a yellow triangle icon. Error - An issue has occurred and may require your attention. Displayed with a red circle icon. Info entries are the most common - they record standard project activity like creating documents, accepting orders, or importing lines. Warning and Error entries surface problems so you can act on them quickly. Info entries are the most common - they record standard project activity like creating documents, accepting orders, or importing lines. Warning and Error entries surface problems so you can act on them quickly. #### What Gets Recorded Project History captures a wide range of events, including: * Project creation, duplication, completion, and cancellation * Quote, invoice, purchase order, and sales order generation * Order acceptance, approval, and decline * Section and workflow changes * Document uploads * Tag additions and removals * Custom validation results (passed or failed) * Webhook delivery attempts #### User Attribution Each history entry shows who performed the action. For actions taken by a user in OE Central, this is the user's name. For actions triggered by an external system or app, the source is identified by a display name - so you can tell at a glance whether an action came from your team or from an integration. ### ๐Ÿ”— **Webhook Tracking** One of the most useful aspects of Project History is its integration with webhooks. When OE Central sends a webhook notification to an external system, the outcome is recorded in history: * A successful send is logged as an Info entry * A failed send is logged as an Error entry, linked to the specific webhook queue record This means you don't need to check external logs to know whether a webhook was delivered. You can see it directly on the project. Resending Failed Webhooks If a webhook fails, the Error entry in history includes a resend option. You can requeue the webhook with a single click, directly from the project history view. OE Central will confirm the action before resending. Once a webhook is successfully resent, the original Error entry is automatically resolved - its link to the failed attempt is cleared, so it no longer shows the resend option. ### ๐Ÿ” **Error Visibility** Projects with unresolved errors are flagged in the workspace, making it easy to identify which projects need attention without opening each one individually. When you open a project's history, entries are sorted with the most recent first. Error and Warning entries stand out visually with their icons, so you can quickly scan for issues. If a project has unresolved webhook errors, you'll see this reflected in the project workspace. Resolving the error (by resending or by a successful retry) clears the flag automatically. ### ๐Ÿ’ก **Why Use Project History Notifications?** Project History Notifications are particularly useful for: * Auditing what happened on a project and when * Diagnosing issues on projects that aren't progressing as expected * Maintaining accountability across teams and automated processes * Identifying failed webhook deliveries without checking external systems * Resending failed webhooks directly from OE Central * Understanding which actions were performed by your team versus external integrations ### โœ… **Summary** Project History Notifications provide a simple but powerful way to: * Track every significant event on a project in one place * Classify events by severity - Info, Warning, or Error * Monitor webhook delivery and resend failures with one click * Identify projects with unresolved errors directly from the workspace * Attribute actions to the correct user, app, or integration This feature gives you confidence that nothing is falling through the cracks - whether it's a team member's action or an automated integration. --- # Agent Instructions: 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: ``` GET https://support.ordereazi.com/sales-features/projects/project-history.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.