Description

Right now title resolution is a foreground process that is long-running and can possibly time out. We want to defer this to the background and have a mechanism to track when it succeeds/fails.

Implementation Considerations

• Some way of storing success/failure status of title resolution in the database
• If two title resolution tasks are kicked off at the same time, which one takes precedence, especially given they run in the background and we can't predict their order.

Deliverable

• When a user adds a title pattern on the frontend, they are shown a message that their title pattern is being resolved
• The user can then track this title pattern and see the status: "pending", "resolved", "failed"
• If some title resolution fails, we need some logs
• A logging model with an admin seems sufficient

Dependencies

No response