Update platform to use upcoming asynchronous ML backend API #505

Activity

1. mihow

   added this to the ML Pipeline Ready for Production milestone on Aug 12, 2024
2. mihow

   self-assigned this

   on Aug 12, 2024
3. mihow commented on Aug 15, 2024

   

   mihow

   on Aug 15, 2024

   CollaboratorAuthor

   More actions

   I have made good progress on this task. The platform has been reworked to accept callbacks and initiate async jobs. With our first image successfully processed by flatbug and the order classifier:

   
4. mihow

   changed the title [-]Update platform to use new ML backend API[/-] [+]Update platform to use upcoming asynchronous ML backend API[/+] on Nov 20, 2024
5. mihow

   modified the milestones: ML Pipeline Ready for Production, ML Pipeline Enhancements, More Models & Backends on Dec 19, 2024
6. mihow

   modified the milestones: ML features v2, ML features v3 on Feb 19, 2025
7. mihow

   added

   PSv2Async & distributed ML backend (PSv2): job state, NATS dispatch, result handling. Umbrella #515.Async & distributed ML backend (PSv2): job state, NATS dispatch, result handling. Umbrella #515.

   on Jun 16, 2026
8. mihow commented on Jun 27, 2026

   

   mihow

   on Jun 27, 2026

   CollaboratorAuthor

   More actions

   Claude says: Closing as completed. The asynchronous ML backend (PSv2) is now the platform default as of #1353 (merged, deployed 2026-06-27): async_pipeline_workers defaults to True and all existing projects were migrated over. The async dispatch path (JobDispatchMode.ASYNC_API — NATS queue, worker pull, result ingestion, cancellation, monitoring) shipped across #987 / #1046 / #1146 / #1162 / #1227 / #1244 and is now the common path. Remaining PSv2 work is tracked as non-blocking follow-ups under the umbrella #515.
9. mihow

   closed this as completedon Jun 27, 2026