Procore Integration Incident Command

Overview

Protect construction data integrity while restoring service. Separate provider outage, identity failure, tenant-routing defect, permission drift, rate exhaustion, event-delivery gap, and internal deployment regression before choosing recovery actions.

Prerequisites

• Incident commander, severity, affected tenant aliases, start time, and objectives
• Current release, last known good release, queue and reconciliation checkpoints
• Procore status, Integration Health, API activity, and approved communication channels

Instructions

Step 1: Stabilize

Pause risky mutations, preserve durable queues, stop retry storms, and keep read-only evidence collection bounded. Do not delete events or rotate credentials without a matching hypothesis.

Step 2: Classify