--- name: halo-scheduling-events description: Design and troubleshoot HaloITSM Calendars and Appointments, Exchange calendar sync, appointment types, resource booking and Event Management alert ingestion, matching, deduplication, and retention. --- # Scheduling and Event Management Read [the operating contract](../../references/operating-contract.md). Identify which record the user is dealing with. A calendar entry schedules a human or planned activity. An Event Management record receives and evaluates an external event. Choose the relevant procedure. ## Calendars and Appointments 1. Identify the calendar owner, viewers, schedulers, time zone, intended appointment type, linked ticket, audience and reminder policy. In **Configuration > Calendars and Appointments > General Settings**, review enabled entry types and agent availability options. When an entry is missing, start with the entry type, appointment type, selected agent/customer, date range and viewing permission. Compare the appointment details on the linked ticket with the calendar before changing synchronization. [Calendars and Appointments](https://www.usehalo.com/guides/880) · [General Settings](https://www.usehalo.com/guides/1837) 2. Create or review a type in **Configuration > Calendars and Appointments > Appointment Types**. Establish required fields, privacy and availability rules, agent status effects and meeting creation when configured. Create a sample from the calendar and a linked ticket when both paths are needed. Check **Private** with an authorized and a restricted observer. Verify where notes, attendees and meeting metadata appear in Halo and the connected calendar. [Appointment Types](https://www.usehalo.com/guides/1836) · [Appointments](https://www.usehalo.com/guides/1939) 3. For user booking, check **Configuration > Calendars and Appointments > Resource Booking** and its booking types. Define booking duration, earliest/latest reservation, eligible staff, shift coverage, clash handling and cancel/reschedule responsibility. Render the booking link in the actual authorized channel. Test competing requests for one slot and the edge of the booking window. [Agent Resource Booking](https://www.usehalo.com/guides/1946) 4. For Exchange synchronization, confirm the integration mode and supported direction on the tenant. Use the Microsoft Graph guide for Graph and the on-prem guide only where its method applies. Map Halo agent, calendar mailbox, calendar ownership, recurring series ownership and approved permissions. Follow inbound/outbound request evidence. Test a private event, modification, recurrence exception, cancellation and daylight-saving boundary with one test calendar before adding others. Check whether calendars have moved before changing matching or immutable ID settings. [Microsoft Graph calendar sync](https://www.usehalo.com/guides/1198) · [On-prem Exchange calendars](https://www.usehalo.com/guides/968) **Diagnostic example.** An appointment created from a ticket is visible in Halo but absent in Exchange. Check the appointment owner and eligibility for sync, then inspect the integration's outbound request for that one event. Compare with a known working owner and verify the intended mailbox and create response. Investigate duplicate series by correlating the existing Halo appointment and provider IDs before re-sending anything. ## Event Management 1. Inventory source system, tenant, environment, ingress payload mode, provider event identifier, allowed fields, severity and recovery semantics, and expected destination ticket type. Use a test source endpoint and safe notification recipients. Check module and Event Management permissions before enabling a feed. [Event Management](https://www.usehalo.com/guides/2305) 2. Start at **Configuration > Event Management > Event Rules > New**. Use the inbound endpoint shown on the current rule page for the verified payload mode. The guide documents JSON-body evaluation and query-parameter evaluation from v2.250. In **Inputs**, map only necessary payload fields into typed variables and build match criteria. Treat external fields as untrusted input. Confirm ingress authentication and retention with the tenant owner before production. Never include secrets or customer content in example requests or in parameters copied to logs. 3. In the event rule's **Ticket Creation** settings, resolve the customer/site/user/asset against stable, appropriate identifiers. Decide the correct action when a mapping is absent or non-unique. For duplicate events, inspect the mapped event ID and the deployed version's create-versus-update behavior. Halo documents **Always create new Tickets** and **New Ticket creation rules** from v2.186. In the pilot, repeat the same event, then send the same condition with a different provider identifier and test recurrence after closure. 4. Use the Event Management log to compare ingress and outcomes. Keep retention periods for matched and unmatched logs explicit under **Configuration > Event Management > General Settings**. For an unmatched event, **Re-evaluate** runs matching again, **Create Ticket** applies a selected rule's outputs, and **Link to Ticket** attaches the event without applying values. Review the side effect before using any of these during recovery. [Event Management](https://www.usehalo.com/guides/2305) **Worked event plan.** For a synthetic disk-space alert, document the source event identifier, asset key, severity and state in a field map. Decide whether repeat warnings update an open ticket and whether recurrence after closure creates a new one. Test missing asset key and severity outside the rule. Inspect the matched rule, associated asset and customer, ticket count, and recipients after each test. If the feed creates unexpected tickets, pause the affected test source, retain minimal correlation evidence and reconcile open tickets before replaying or switching back. ### Follow an event from a connected ticket Resolve the exact ticket and asset first. Record the event provider's redacted correlation key, expected event state and one bounded time window. If the connection exposes only tickets and assets, obtain the rule match, retained event status and provider acknowledgement from their respective logs. For an appointment, obtain the provider event or series ID and verify visibility or invite delivery in the target calendar. A ticket or appointment record confirms its Halo state. Re-evaluation, ticket creation, calendar invitations and cancellation are separate actions with their own effects. [Event Management](https://www.usehalo.com/guides/2305) · [Calendar sync](https://www.usehalo.com/guides/1198) ## Acceptance checklist | Change | Positive and adverse cases | Evidence | | --- | --- | --- | | Appointment type | Book, reschedule, cancel, show free/busy to a restricted observer | One intended entry, correct local time and allowed details | | Calendar integration | Create and modify in each intended direction, recurring exception, private entry | Linked IDs and expected permissions and invitations in both systems | | Booking | In-window slot, outside hours, collision, cancel | One assignment, predictable availability and permitted recipients | | Event rule | Match, ignore, unknown asset, retry same event, recurrence after closure | Expected event status, ticket count, association, action and recipients | | Revert | Restore prior calendar or event rule and re-run known-good case | Original behavior restored. Already sent invitations or created tickets have a documented reconciliation owner |