Feed processing fails after Craft 5 update, requires resaving of feed config

[ul8]

Description

When running a feed after a Craft 5 upgrade, logs show errors like this one:

Setting unknown property: craft\elements\db\EntryQuery::field_plainText_zluajmrs - Component.php: 217.

Steps to reproduce

1. Update a site with feeds from Craft 4 to Craft 5
2. Try running a feed. It fails.
3. Open the feed's configuration and save each configuration page (no changes necessary)
4. Once the field mapping page has been saved, run the feed again
5. The feed works once again without issue.

As you can see the workaround is an easy one so nobody else might be reporting this bug.

Additional info

• Craft version: 5.5.2
• PHP version: 8.3
• Database driver & version: MariaDB 10.4
• Plugins & versions:
  "born05/craft-sentry": "3.0.0",
  "craftcms/ckeditor": "4.4.0",
  "craftcms/cms": "5.5.2",
  "craftcms/feed-me": "6.5.0",
  "craftcms/mailgun": "3.1.0",
  "craftcms/redactor": "4.2.0",
  "doublesecretagency/craft-cpcss": "3.0.0",
  "fredmansky/craft-pdf-renderer": "1.3.1",
  "fredmansky/craft-proper": "1.6.1",
  "goldinteractive/craft-sitecopy": "2.1.1",
  "guzzlehttp/guzzle": "7.9.2",
  "mmikkel/cp-field-inspect": "2.0.2",
  "nystudio107/craft-emptycoalesce": "5.0.0",
  "nystudio107/craft-retour": "5.0.3",
  "nystudio107/craft-seomatic": "5.1.6",
  "nystudio107/craft-templatecomments": "5.0.3",
  "nystudio107/craft-twigprofiler": "5.0.0",
  "nystudio107/craft-vite": "5.0.1",
  "putyourlightson/craft-blitz": "5.9.6",
  "putyourlightson/craft-elements-panel": "3.0.0",
  "spacecatninja/imager-x": "5.0.3",
  "studioespresso/craft-dumper": "5.0.1",
  "ttempleton/craft-nocache": "3.0.4",
  "verbb/expanded-singles": "3.0.1",
  "verbb/field-manager": "4.0.3",
  "verbb/formie": "3.0.12",
  "verbb/hyper": "2.2.0",
  "verbb/image-resizer": "4.0.1",
  "verbb/smith": "3.1.0",
  "verbb/tablemaker": "5.0.3",
  "vlucas/phpdotenv": "5.6.1"

[vardumper]

I ran into exactly the same issue. As of Craft 5.6 and FeedMe 6.7: I can confirm it is still around. Thanks for this issue. You probably saved me some time.