Repository navigation
Better logging on 422 errors #1580
Description
When running plans on i15-1 we're occasionally getting 422 errors in blueAPI:
2026-06-30 09:18:16,779 INFO bluesky.RE.state Change state on <bluesky.run_engine.RunEngine object at 0x7fe173e31990> from 'running' -> 'idle'
2026-06-30 09:18:16,780 INFO bluesky Cleaned up from plan <generator object sleep at 0x7fe0c2271700>
2026-06-30 09:18:16,780 INFO blueapi.worker.task_worker Task ran successfully - returned: None
2026-06-30 09:18:16,781 INFO blueapi.worker.task_worker Awaiting task
2026-06-30 09:18:17,885 INFO blueapi.service.main ::1:48356 GET /worker/state 200
2026-06-30 09:18:19,063 INFO blueapi.service.main ::1:48362 GET /worker/state 200
2026-06-30 09:18:20,245 INFO blueapi.service.main ::1:48370 GET /worker/state 200
2026-06-30 09:18:20,554 INFO blueapi.service.main ::1:48382 POST /tasks 422
2026-06-30 09:18:21,426 INFO blueapi.service.main ::1:48384 GET /worker/state 200
2026-06-30 09:18:22,611 INFO blueapi.service.main ::1:48390 GET /worker/state 200
2026-06-30 09:18:23,794 INFO blueapi.service.main ::1:48392 GET /worker/state 200
To diagnose these it would be good to have some logging as to what was POSTed and why it failed.
This can be reproduced locally by running the UI against a local BlueAPI and sending a selection of different plans.
Acceptance Criteria
- On 422 errors there is better logging
Activity