Confuse about "Invalid Field falling back to"

Our metabase is on 0.41 now, after upgrade, we got thousent of warning log about tell me that field type invalid when fire a query.
log looks like this, but everything seem ok. And I wonder why it popup and how to fix it either

2021-10-14 17:16:23,812 WARN models.field :: Invalid Field:semantic_type:type/Number:falling back tonull
2021-10-14 17:16:23,812 WARN models.field :: Invalid Field:semantic_type:type/Number:falling back tonull
2021-10-14 17:16:23,812 WARN models.field :: Invalid Field:semantic_type:type/Number:falling back tonull
2021-10-14 17:16:23,812 WARN models.field :: Invalid Field:semantic_type:type/Number:falling back tonull
2021-10-14 17:16:23,812 WARN models.field :: Invalid Field:semantic_type:type/Number:falling back tonull
2021-10-14 17:16:23,812 WARN models.field :: Invalid Field:semantic_type:type/Number:falling back tonull
2021-10-14 17:16:23,812 WARN models.field :: Invalid Field:semantic_type:type/Number:falling back tonull
2021-10-14 17:16:23,814 WARN models.field :: Invalid Field:semantic_type:type/Number:falling back tonull
2021-10-14 17:16:23,814 WARN models.field :: Invalid Field:semantic_type:type/Number:falling back tonull
2021-10-14 17:16:23,814 WARN models.field :: Invalid Field:semantic_type:type/Number:falling back tonull
2021-10-14 17:16:23,814 WARN models.field :: Invalid Field:semantic_type:type/Number:falling back tonull

Hi @KEN-LJQ
The field type Number was removed in 0.40.0 in the backend, and in 0.40.2 from the frontend.
You can change the type to null or one of the other available types in the application database table metabase_field.semantic_type
For reference:
https://github.com/metabase/metabase/pull/15994
https://github.com/metabase/metabase/issues/16781

it will be nice to migration instruction after changes :wink:
otherwise troubleshooting is happened