super-table icon indicating copy to clipboard operation
super-table copied to clipboard

Queue: Setting unknown property: verbb\supertable\fields\SuperTableField::propagationKeyFormat

Open heymarkreeves opened this issue 2 years ago • 5 comments

Description

We're consistently seeing failed "Updating search indexes" jobs in the queue, with the following error:

Setting unknown property: verbb\supertable\fields\SuperTableField::propagationKeyFormat

Additional info

  • Plugin version: 2.7.1
  • Craft version: 3.7.34
  • Multi-site: No

Additional context We observed these dating back to April last week. I released all of the failed jobs yesterday and we're back to 1,196 of these already. We last updated Craft & plugins in March and that's something we have to schedule and work toward in advance, so it's not a quick fix option. We're wondering if there's anything identifiable from this error or that you can point us towards.

heymarkreeves avatar Jun 07 '22 19:06 heymarkreeves

Are you sure those are the versions you're on, or have you recently upgraded to these versions after these queue jobs were created? 2.7.2 is worth updating to, but propagationKeyFormat as a property has been around since 2.7.0 inline with Craft 3.7 changes

engram-design avatar Jun 08 '22 02:06 engram-design

Those are the versions I saw in the control panel yesterday—and just confirmed in composer.json, and we haven't run updates since March, when we updated to 2.7.1.

heymarkreeves avatar Jun 08 '22 11:06 heymarkreeves

Hmm, so after clearing out the queue jobs, you're still getting this error on the new versions of everything? Are you able to look in your /storage/logs folder and search your log files for this error Setting unknown property: verbb\supertable\fields\SuperTableField::propagationKeyFormat to show the full stack trace of the error?

engram-design avatar Jun 08 '22 11:06 engram-design

I'm not seeing any queue.log entries that match failed jobs. I only see 1 error in queue.log, and that's unrelated to these.

heymarkreeves avatar Jun 08 '22 16:06 heymarkreeves

Strange, even if you try and re-run the failed queue jobs? Just trying to track down exactly where this error is being triggered from. I would also check your other log files like web.log just in case

engram-design avatar Jun 08 '22 21:06 engram-design