Skip to content

Commit 0f03e92

Browse files
authored
Merge pull request #87932 from Juliako/patch-112
Update media-services-release-notes.md
2 parents 4c14b3b + e4b7fed commit 0f03e92

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/media-services/previous/media-services-release-notes.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ These release notes for Azure Media Services summarize changes from previous rel
2525
2626
We want to hear from our customers so that we can focus on fixing problems that affect you. To report a problem or ask questions, submit a post in the [Azure Media Services MSDN Forum].
2727

28-
## <a id="issues"/>Currently known issues
28+
## <a id="issues"/>Known issues
2929
### <a id="general_issues"/>Media Services general issues
3030

3131
| Issue | Description |
@@ -37,6 +37,7 @@ We want to hear from our customers so that we can focus on fixing problems that
3737
| When you query entities, a limit of 1,000 entities is returned at one time because the public REST version 2 limits query results to 1,000 results. |Use Skip and Take (.NET)/top (REST) as described in [this .NET example](media-services-dotnet-manage-entities.md#enumerating-through-large-collections-of-entities) and [this REST API example](media-services-rest-manage-entities.md#enumerating-through-large-collections-of-entities). |
3838
| Some clients can come across a repeat tag issue in the Smooth Streaming manifest. |For more information, see [this section](media-services-deliver-content-overview.md#known-issues). |
3939
| Media Services .NET SDK objects can't be serialized and as a result don't work with Azure Cache for Redis. |If you try to serialize the SDK AssetCollection object to add it to Azure Cache for Redis, an exception is thrown. |
40+
|The REST API responds with an error message saying “The filter cannot be accessed by this version of REST Api” when attempting to get an Asset or Account level filter.|The filter was created or modified with a newer API version than is being used to try to get the filter. This can happen if two API versions are being used by code or tools being used by the customer. The best solution here is to upgrade the code or tools to use the newer or the two API versions.|
4041

4142
## <a id="rest_version_history"/>REST API version history
4243
For information about the Media Services REST API version history, see the [Azure Media Services REST API reference].

0 commit comments

Comments
 (0)