This is probably a bit late, but for people that stumble on this problem: we noticed that flushing the cache immediately after creating an integration gets rid of this problem.

So:

- create an integration

- flush all caches

- activate the integration

That solved this problem for us.

It sounds like a bug in Magento, but I haven't tested it on the latest version, so not sure if it's still a bug or not.