Transient errors during Win32 app creation

[tjgruber]

During a run of five simultaneous pipeline Intune app updates, two of them experienced different errors at the same step of the process:

VERBOSE: Attempting to create Win32 app using constructed body converted to JSON content
VERBOSE: POST https://graph.microsoft.com/Beta/deviceAppManagement/mobileApps
WARNING: An error occurred while creating the Win32 application. Error message: DQCancelledOnRequestTimeout: {
  "_version": 3,
  "Message": "An error has occurred - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: <redacted>(https://github.com/<redacted>/<redacted>/actions/runs/<redacted>/job/<redacted>?pr=<redacted>#step:6:82)<redacted> - Url: https://fef.msua08.manage.microsoft.com/AppLifecycle_2406/StatelessAppMetadataFEService/deviceAppManagement/mobileApps?api-version=5024-03-08",
  "CustomApiErrorPhrase": "",
  "RetryAfter": null,
  "ErrorSourceService": "",
  "HttpHeaders": "{}"
}

VERBOSE: Attempting to create Win32 app using constructed body converted to JSON content
VERBOSE: POST https://graph.microsoft.com/Beta/deviceAppManagement/mobileApps
WARNING: An error occurred while creating the Win32 application. Error message: InternalServerError: {
  "_version": 3,
  "Message": "An internal server error has occurred - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: <redacted> - Url: https://fef.msua08.manage.microsoft.com/AppLifecycle_2406/StatelessAppMetadataFEService/deviceAppManagement/mobileApps?api-version=5024-03-08 - CustomApiErrorPhrase: viderHelpers0cDisplayClass100ExecuteNonQueryStoredProcedureAsync",
  "CustomApiErrorPhrase": "viderHelpers0cDisplayClass100ExecuteNonQueryStoredProcedureAsync",
  "RetryAfter": null,
  "ErrorSourceService": "",
  "HttpHeaders": "{}"
}

Simply re-running the failed jobs resulted in success.

This hints towards a temporary service interruption or some other temporary issue such as throttling, etc.

To prevent this from happening in the future, if it is indeed temporary issues like thought, perhaps adding retry logic during this step of the app creation (and possibly other steps), might prevent something like this from stopping future runs.