The managed APIM developer portal publication fail, how to know the root cause of failure.

Question

I cannot publish the last modification on the APIM developer portal. I need to know what is the cause of the failure to fix it. How can I get logs or any information about the reason of the failure ?

Answer 1

Hi @Gregory Tall You can enable Diagnostic logs on the API Management service instance and capture the logs related to Developer portal usage and save it to an end point to capture additional logging. Please refer the below image where this setting can be enabled.

The following article Enable Developer Portal Usage logs will guide you with the steps on how you can enable this setting.

Only Portal requests in Completed status can be set IsCurrent

The message indicates the you are trying to set a revision of API version whose portalRevisionStatus is not completed. An API revision status can be in any of the following three states other than being completed

1. In Progress: The revision is still being processed. This can happen if the changes are large or if there is a high load on the service.
2. Failed: The revision process encountered an error. This could be due to issues with the changes being applied, such as invalid configurations or conflicts with existing settings.
3. Pending: The revision is queued and waiting to be processed. This can occur if there are multiple revisions being applied simultaneously or if the service is experiencing high demand.

You can validate the details of the revision status by calling the API end point Portal Revision - Get and passing the correct revision Id.

If you have access to the API management service instance through Azure portal, follow the steps provided Add revisions through the portal and Make your revision current and add a change log entry

Hope this helps! Please let us know if you have additional questions or need further assistance.