Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.younegotiate.com/llms.txt

Use this file to discover all available pages before exploring further.

Real-World Example

Jane changes an installment payment date. The portal updates the internal schedule immediately and then dispatches a background job so Google or Microsoft Calendar receives the same date change.

Visual Flow

How It Should Work

  • It should create, update, delete, or change amounts on external events when live sync is enabled.
  • It should keep the internal schedule as the source of truth.
  • It should handle Google and Microsoft sync without blocking the consumer page.

How It Should Not Work

  • It should not let a calendar job change payment truth by itself.
  • It should not fail the main payment action only because an external calendar provider is unavailable.
  • It should not update events for consumers who disabled live sync.

Developer Notes

  • Calendar jobs are dispatched from schedule changes, payment processing, and calendar connection flows.
  • Use queue-safe, idempotent handling because the same payment can be touched by multiple flows.
  • app/Jobs/CreateCalendarEvents.php
  • app/Jobs/UpdateCalendarEvents.php
  • app/Jobs/UpdateCalendarEventAmount.php
  • app/Jobs/DeleteCalendarEvents.php
  • app/Livewire/Consumer/SchedulePlan.php
Last modified on May 25, 2026