Function Deployments Stuck in Queued State

The team is actively working on a fix for this issue and has recommended the following workaround for affected users.

This issue may occur if multiple Functions are deployed simultaneously. To mitigate this, users are advised to limit the number of Functions deployed at the same time.

Additionally, users working with GitHub or ADO workflows are advised to enable the following settings:

• GitHub Workflows: Set continue-on-error: true

• ADO Workflows: Set continueOnError: true for the specific task or job in your YAML pipeline definition

Note:
Enabling continue-on-error /continueOnError ensures that other function deployments proceed even if one fails, helping maintain efficient deployment workflows.

The team was able to narrow down the issues related to the errors and are currently in the fixing stage.

Reopening this incident as we are still observing mixed results with recent function deployments. While many deployments have succeeded, several are still failing.

Failures include 403 and 404 errors during function deployments. If you are experiencing this, we recommend waiting 30 minutes to a few hours before retrying. Repeated attempts without waiting can worsen the situation.

The system has remained stable for over 12 hours, and no further issues have been observed.

Currently, we are experiencing a partial outage in the Functions API Services, where the new deployments are queued indefinitely.
This only affects the new function deployments. All existing deployments are working as expected.