-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Description
The bug of tickets from the community not showing up on our website in cases of old organizations has been identified. Details of the issue can be found [here].
After conducting an RCA, we decided to set up a CRON job to periodically push all available ticket information into our servers at a defined frequency (to be determined). This will serve as a backup mechanism to the existing webhooks and not as a replacement
Key Considerations:
- CRON frequency: Identify an optimal schedule to balance data freshness with server load.
- Data consistency: Ensure CRON jobs do not create duplicate entries or overwrite legitimate updates from the webhook.
Success Criteria:
- Mechanism in place to differentiate tickets marked out of scope/'to be deleted' earlier by PT coming in with new CRON.
- To Maintain a source-of-truth table to reconcile data discrepancies post CRON processing.
- Logs to be added for all CRON runs - success and failures
Metadata
Metadata
Assignees
Labels
No labels