Through local experimentation I found that the runtime exception is caused by examples that contain a retry-after header in the response with an integer value.
The retry-after header is defined in the REST API as type: integer, format: int32 so it makes sense to specify it in the example as an integer value.
The Breaking Change (Cross-Version) check in PR 21841 fails with an oad runtime exception:
Through local experimentation I found that the runtime exception is caused by examples that contain a
retry-afterheader in the response with an integer value.The
retry-afterheader is defined in the REST API astype: integer, format: int32so it makes sense to specify it in the example as an integer value.