Definition: What is PARS Resubmit?
PARS Resubmit is a technical mechanism used to retransmit calendar data to integration partners. Its primary purpose is to resolve synchronization discrepancies between internal systems and external partner platforms.
Core Logic: Batch Processing
To maintain system stability and prevent timeouts during peak loads, PARS Resubmit operates using a batching logic rather than processing all data simultaneously.
- Method: Splits large data tasks into smaller chunks based on calendar days.
- Stability: Prevents system overloads when handling multiple hotels, partners, and extensive date ranges.
Request Triggering and Date Logic
Resubmit requests can be initiated via the Admin application or ChannelManager at various levels (partner-wide or hotel-specific). The system processes dates based on two distinct windows:
Immediate Processing (Sync)
- Range: Today up to 7 days in the future.
- Behavior: Processed immediately and synchronously to ensure the most urgent data is updated instantly.
Background Processing (Async)
- Range: Dates beyond 7 days (up to a default of 730 days/2 years).
- Behavior: Split into batches of 30 days each and saved to the database for background processing.
Exception: Single Mapping Resubmit
Requests triggered for a single mapping within ChannelManager bypass the batching queue. These are processed immediately due to their minimal resource impact.
The 3-Step Batch Processing Workflow
A dedicated background service processes queued batches using the following sequence:
- Step 1: Cleanup: Deletes existing distribution logs for the specific period/mapping. Large deletions are performed in chunks to avoid system hangs.
- Step 2: Generation: Creates new distribution logs based on current system data.
- Step 3: Validation & Retry:
- Success: Batch is marked as processed.
- Failure: The system attempts up to 10 retries with exponential backoff (increasing wait times).
- Final Failure: After 10 failed attempts, the batch is marked as Failed.
Monitoring and Troubleshooting
Users can track the lifecycle of a resubmit request through two primary interfaces:
Resubmit Status View: Displays the status of batches. Users can filter by partner or date range. If a batch fails, the first troubleshooting step is a manual Retry.
Progress Bar View: Displays the actual Distribution Logs. These logs represent the data being sent to the partner. Note: Logs only appear here after the background batch processing is complete.
Key Terms Summary
- Batch: A 30-day segment of calendar data used for processing.
- Distribution Log: The actual data packet transmitted to a partner.
- Sync Window: The first 7 days of a request processed in real-time.
- Retry Limit: 10 attempts before a batch is declared invalid.