Why polling?
When borrowers interact with the Borrower Dashboard Element, the loan progresses through various stages and tasks are completed. To keep your application in sync with these changes, you need to poll the GraphQL API to detect:- Loan stage transitions (e.g., “Underwriting” → “Conditionally Approved” → “Clear to Close”)
- New task assignments
- Task completions
- Document uploads
- Disclosure status changes
- Order-out status updates (appraisal, title, etc.)
Recommended polling intervals
| What to monitor | Recommended interval | Detection method |
|---|---|---|
| Loan stage | 15-30 minutes | Compare currentStage |
| Tasks | 15-30 minutes | Track task IDs and status |
| Documents | 30-60 minutes | Track uploadedAt timestamps |
| Order-outs (appraisal/title) | 2-4 hours | Check orderStatus fields |
| Disclosure status | 30-60 minutes | Check signed fields |
Basic polling implementation
Here’s a simple example that polls for loan stage changes:Monitoring tasks
Poll for new tasks and task status changes:Monitoring order-outs
Track appraisal and title order status:Complete polling guide
For comprehensive polling patterns, implementation examples, and best practices, see the Tracking loan updates guide. That guide covers:- Focused queries for efficient polling
- State management and change detection
- Error handling and retry logic
- Polling multiple loans
- Monitoring different entity types (stages, tasks, documents, order-outs, etc.)
Best practices
- Use focused queries - Only request the fields you need to detect changes
- Store previous state - Cache values you’re monitoring to detect changes
- Handle errors gracefully - Implement retry logic for transient failures
- Adjust intervals by entity - Poll stages/tasks more frequently than order-outs
- Stop polling when done - Clear intervals when loans are closed or no longer need monitoring
Next steps
- Tracking loan updates - Complete polling guide with examples
- Customize the theme - Style the Element
- Loan Application Element - For new applications