My integration didn’t sync a key

Check the provider connection, environment mapping, and sync issues.

Why it happens

A key may be skipped if its environment is unmapped or its name is invalid for the provider. A sync can also stop because the connection needs attention or the provider already has a conflicting value.

What to do

  1. Open the affected integration in the project. Verify the provider connection, target, and environment mapping for the key.
  2. Check the reported sync issue and follow the relevant provider guide. Review conflicts before changing anything on the provider.
  3. Choose Sync now, review the proposed changes, and apply them. For a custom-encrypted project, provide the vault key when prompted.

Check the result

Check that the issue clears in ApiVault and that the key name appears in the expected target environment on the provider. If the provider uses values at deployment time, follow its guide to make the change live.

Still stuck? Contact support with the error and the steps you tried. Remove secret values before sending.