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’s failed installment is moved to the end of the plan after an auto-skip. The payment schedule changes in the portal first, then calendar sync jobs update or delete the old external calendar event and create the new one when live sync is enabled.Visual Flow
How It Should Work
- It should keep external calendar events aligned when payment jobs move, skip, delete, or complete scheduled transactions.
- It should run after the portal schedule is updated.
- It should handle provider errors without corrupting payment state.
How It Should Not Work
- It should not make external calendars the source of truth for payment schedules.
- It should not update external events when the consumer has not enabled live sync.
- It should not create duplicate events for schedule transactions already synced.
Developer Notes
- Calendar sync is touched by manual schedule changes and background installment jobs.
- Create, update, amount update, and delete jobs should stay idempotent.
Related App Areas
app/Jobs/CreateCalendarEvents.phpapp/Jobs/UpdateCalendarEvents.phpapp/Jobs/UpdateCalendarEventAmount.phpapp/Jobs/DeleteCalendarEvents.phpapp/Jobs/SkipScheduleTransactionJob.phpapp/Console/Commands/RestartPaymentPlanCommand.php