My automation has been successfully running the following mutation daily for weeks:
```
mutation updateItem($board_id: ID!, $item_id: ID!, $column_values: JSON!) {
change_multiple_column_values(
board_id: $board_id
item_id: $item_id
column_values: $column_values
) {
id
}
}```
With the following variables:
```
{
"board_id": 8767955035,
"group_id": "topics",
"column_values": "{\"date4\":\"2026-07-24 00:00:00\"}",
"item_id": "8954255421"
}```
The `group_id` variable is set, but not used, so this is just a red herring.
Today when it ran, I got the following response:
```
{
"data": {},
"errors": [
{
"message": "Unauthorized field or type",
"path": [
"change_multiple_column_values"
],
"extensions": {
"code": "UNAUTHORIZED_FIELD_OR_TYPE"
}
}
],
"extensions": {
"request_id": "601955a7-20fb-9f36-badf-826dbf31145e"
}
}```
Nothing has changed on the app, automation, or board, but today it failed.
Running the same mutation in the GraphQL playground works just fine.
Could mdc have quietly changed the permission on the app, removing the workspace permission?
The last time i wrote an almost identical question, it was because board:write permissions were missing, but this is not the case.
Could there be a temporary glitch in board:write permission?