This line shows up in WooCommerce → Status → Logs from Meta for WooCommerce (formerly Facebook for WooCommerce), often many times with the same timestamp. It means one thing: the store has no stored connection to Meta right now, so nothing can be sent to your catalog or your pixel.
Error ProductSetSync exception: ... Cannot create the API instance because the access token is missing.When you connect the store in Marketing → Facebook, Meta gives the plugin an access token and the plugin saves it in the database. Every request to Meta - product updates, product sets, the catalog feed - is made with that token. The error comes from the plugin's own code: whenever something tries to talk to Meta and the saved token is empty, it stops with exactly this message.
So the error is not the problem itself. It is the plugin telling you the connection is gone.
Background tasks keep trying to reach Meta on their normal schedule. The product-set sync, for example, works through your product categories one by one, and each attempt fails the same way - so one missing token becomes one log line per category, all with the same time. It is one problem.
The token is only ever removed or never saved; common ways that happens:
If connecting itself fails or loops back to the start, the usual causes are a security plugin blocking the REST API, or a firewall blocking requests to facebook.com from your server.
StallRadar Sync Doctor for Meta for WooCommerce is a free plugin that checks the connection, the catalog and pixel, the product feed file, Meta's background jobs and its logs, and tells you in one line what is blocking the sync and how to fix it. It will be submitted to WordPress.org soon; until then the same build can be downloaded here.
Download the free pluginNot affiliated with Meta, Facebook or WooCommerce.
No. Your products are still in WooCommerce, and the catalog on Meta keeps what it had. Nothing is updated until the store is connected again.
One background task tried to reach Meta once per product category and failed the same way each time. It is one problem, not dozens.
You can, but they come back on the next sync attempt until the store is connected again. The log is reporting the problem, not causing it.