@NickMontagu If you look again, those errors appear to have been resolved.
I'm guessing you saw them before they got automatically resolved. Here's a little explanation:
First, when retrieving errors from /sync-errors, you can provide an optional query param showResolvedErrors=true, and you can see the error for extId 7 was resolved.
Second, the error type SETTINGS_NOT_ENABLED is about what you guessed it was. You're using the ecommbridge api on this portal directly, so this error means:
No sync settings were found for the portal
Or sync settings were found, but they were not enabled
Third, i'm guessing you did things in this order:
Created settings, which were not enabled
Sent sync messages, like for extId 7
Enabled your ecomm settings
Since at #2 they weren't enabled, they didn't get synced.
But we store all sync messages that fail and attempt to retry them. When we retry is a big number.. like 1.5 days.
So then
The sync messages were retried, and now that settings were enabled, they synced properly
You could have also just sent the same sync message over if you didn't want to wait.
Thinking it over, there's also a delay between Ecomm setting changes and them being picked up by the sync process.
Is it possible that you set the settings to enabled, and then for a time after things seemed to not work?
Basically, we cache settings, and it refreshes something like.. every 30 minutes