Eric Pugh

It seems to happen when I directly use `perform_later`, however I have a [nightly recurring](https://github.com/o19s/quepid/pull/1039/files#diff-e02d060e76a92603bab92088890870d4c859fb237e9ccc4283766ca579acdddb) job that doesn't seem to have the same issue. I'm wondering if it's some sort...

I wanted to follow up as I gave my team the demo of the branch that uses Solid Queue, and looking forward to merging and deploying it once we get...

Likewise is that I've been using bin/jobs recently... And things have been reliable... I did also set all the settings back to the defaults.. I'll keep you posted on this!

thanks for looking into this...! Whatever fields you have shown in the main page *should* be recorded... Could you show waht the main page with the search results looks like?...

There has been some bug fixes that you might want to pick up and see if it works the way you want. Yeah, we don't have any kind of sampling,...

So, we started with a client doing chunk eval for a RAG project using Quepid.... We're now looking at LLM powered judgements being used in Quepid... We are seeing that...

Bumped into this too..

https://github.com/excid3/noticed for updating folks on events?

A lot has been done.. We have first party analytics via Ahoy, and Blazer for telling us interesting things. cAlling this good enough for now.

Apparently we need a https://api.rubyonrails.org/classes/ActionController/Redirecting.html#method-i-redirect_back_or_to