Specific status' not being filtered

[JayBox325]

Describe the bug

I have setup a "maybe" status for my client, and they've used it in a few places, but when they try to filter the submissions view by this status, it returns no results. What can I do to re-index submissions or update this?

Steps to reproduce

1. Create custom status'
2. Use them
3. Try to filter

Form settings

• Multi-page form: Yes
• Submission Method: Headless with Graphql
• Client-side Validation: Yes
• Custom Form Templates: Yes

Craft CMS version

5.8.15

Plugin version

dev-craft-5

Multi-site?

Yes

Additional context

No response

[engram-design]

That's strange; it certainly is filtering for me. Was the status created before or after the submissions came in? It shouldn't matter, but just in case...

Does going into the submission and re-saving change anything? What about toggling to another status, saving, then toggling back to "Maybe"?

[JayBox325]

I knocked one back into 'new', saved it. Then put it back into 'maybe' and it's still not showing in the Maybe results. I also created a new submission, marked it as "maybe" and got the same result.

[JayBox325]

I have just tried to run php craft resave/formie-submissions --update-search-index and it looked to be working, but then I hit:

    - [60/544] Resaving 2025-12-30 00:10:23 (6264) ... PHP Fatal Error 'yii\base\ErrorException' with message 'Allowed memory size of 268435456 bytes exhausted (tried to allocate 24576 bytes)'

in /srv/app/bristoltattooexp/htdocs/vendor/yiisoft/yii2/caching/FileCache.php:117

Stack trace:
#0 [internal function]: yii\base\ErrorHandler->handleFatalError()
#1 {main}

I think I might have to just make a fresh status locally and push that up, which isn't ideal for my client - but it's a solution for now.

[engram-design]

Yeah, this is pretty odd - I can't seem to replicate what you're seeing with these statuses. So, resaving those submissions from the command line was working (until the memory issues)? I don't believe status is something on the search index.

Any other statuses (if you have them) work? Just wondering if it's maybe something unique to that status.

[JayBox325]

We have got many status' and they all work except that one. So my only potential resolution to this is to just make a new status and try then?

[engram-design]

Yeah, right, that's indeed a little strange. I know there can potentially be issues (in the past) with statuses created locally, and pushed to production with project config, so I wonder if there's some sort of mismatch there. Although statuses are compared by the handles, so I wouldn't have thought so.

Re-creating the status might be a "quick" fix, although a bit of a pain to re-assign things.

But it might be worth checking if there's a difference between the statuses on production and local - by some chance that's messing things up.

Navigate to /admin/formie/settings/statuses on both environments, and see if their IDs are different for the "Maybe" status.

[JayBox325]

The problem here is that statuses are not editable on my production environment and are only managed with project config for some reason so I can't see them on the production site without enabling admin changes.

For me, statuses shouldn't be project level config as I'm using the same repo for 3 sites (same client that wanted 3 sites and not using the multi-site setup), so when these need to be changed it's not a great AX to have to come to me for this, so if it's possible to manage statuses not requiring me to do it, that would be beneficial.

[engram-design]

So you should be able to browse to them on production with that link directly (you just can't edit anything), and indeed, navigating via the UI won't work.

And yeah, that's the downside of project config - I totally get it. We'll have to look at detaching statuses, as well as a few other things (integrations, captchas, etc) that have proven more of a hassle being in project config than not.