Hélène Martin

Converted back to draft while we explore an [alternative concept](https://docs.google.com/document/d/1re5ppNH34qBtt6bQS4ClbvFrlFsDEFfDjpk1NVwdwKo/edit?tab=t.owxltkbhvfsu).

It didn't ring a bell when you mentioned it but now I'm pretty sure this was @lindsay-stevens pushing the limits with `pyodk`. I think we discussed with @matthew-white and decided...

Well, could we surface the error and not do anything instead of crashing? Maybe that's not any easier than just supporting that case?

I want to be clear that I agree the crash should be prevented so glad to see #1158! I was also initially being fooled by the Docker restart.

> I thought this is where it was best discussed Feels right! We generally recommend [the ODK forum](https://forum.getodk.org/) as a good starting point for questions so that they get more...

Another quick thought -- depending on what your needs are, you could consider using a text field before your select multiple and a `choice_filter` using [`contains()`](https://docs.getodk.org/form-operators-functions/#contains), [`starts-with()`](https://docs.getodk.org/form-operators-functions/#starts-with), etc to filter...

Capturing some quick initial thoughts that I will chew on for a bit: - the behavior is nice. It serves the primary goal of clients not needing to follow redirects....

Have heard a couple of requests for OData feed of combined audit.

Another request: https://forum.getodk.org/t/what-is-the-odata-endpoint-to-get-client-audit-json/51539 Questions: should we support filtering and pagination? It can get very big. Could start by not supporting encrypted forms

We're now feeling pretty confident we have configurations that maximize safety for each part of the system. We're going to monitor reports from this upcoming release and open a new...