Intermittent Missing Custom Meta Tags and Blank Sections on Drupal Pages After Frequent Content Updates

That is definitely a weird error.

I suggest you first upgrade your codebase to the latest D10 (or 11) and Metatag 2 releases, and see if the problem persists.

Thank you for the suggestion. We will definitely take this suggestion and upgrade and will see if the issue persists.

However, we have noticed that this issue does not occur in our UAT environment or when Drupal is running on a single instance, but only in multiple server instances (in load balancer setup). Are there any specific pointers in terms of configuration we might have overlooked when it is a load balancer environment.

Thanks

That is really odd.

You might look to make sure the caching is working correctly, in particular that each environment is correctly able to access the caching system - presuming you're using memcache or redis.

Thanks for the suggestions. Wanted to share a few additional observations.
As mentioned earlier , after frequent content updates in the cms backend, we sometimes getting the following errors

1. Error: Undefined constant "Drupal\node\Entity\DRUPAL_OPTIONAL" in Drupal\Core\Entity\EntityStorageBase->mapFromStorageRecords() (line 452 of core/lib/Drupal/Core/Entity/EntityStorageBase.php)
2. PHP Exception InvalidArgumentException: "Field body is unknown." at core/lib/Drupal/Core/Entity/ContentEntityBase.php line 587
3. Additionally, some fields disappear on certain content types, leaving only the title visible.

Would appreciate any guidance or insights you might have on these issues.

That seems like something is failing badly and caches are being rebuilt while content is saving.

Do you have memcache, redis or something else set up as a cache backend?

Do you have any custom code that interacts with the cache system?

Currently, we don't have memcache or Redis set up as a cache backend yet and we are using the database as the cache backend at the moment.
Yes, we are using custom code to store one of the API response in the cache. There is no other custom code interacting with the cache system beyond this API response caching. Please let us know if the custom code can create an issue.

Thanks,