- The CA API Gateway ("Gateway") may not sync applications with the CA API Developer Portal ("Portal") when legacy Portal bundles are used on the Gateway.
- Bundles affected are those built pre-March 2016.
- This issue can affect Gateway nodes integrated with Portal version 4.2.7 in SaaS environments (released June 11 & 12, 2018), and Gateway nodes integrated with on-premise Portal version 220.127.116.11, specifically if the Gateway nodes are using a Portal bundle dated prior to March 2016.
- This issue is caused by a mix of older Portal bundle versions/build dates, and a table name change in the database.
- Update the Portal bundle on the Gateway to the latest version.
- It is considered best practice to update the Portal bundles during the upgrade process, as noted in the documentation. This issue should not be seen as long as that best practice is followed.
- The process of updating the Portal bundle on the Gateway involves a restart of the Gateway service on each node in the cluster before it takes effect.