GraphQL Cache Response Post Update

[PhillipJacobs]

Is there a server side cache for GraphQL queries? We use GraphQL API to get initial data list, made some updates using REST API and then when we rerun the graphQL statement the changes are not reflected.

For example with module item external URLs:

query listCourseModuleItems($courseId: ID!, $nextCursor: String!) {
  course(id: $courseId) {
    modulesConnection(first: 50, after: $nextCursor) {
      nodes {
        moduleItems {
          _id
          content {
            ... on ExternalTool {
              url
            }
          }
        }
        _id
      }
      pageInfo {
        endCursor
        hasNextPage
        startCursor
      }
    }
  }
}

If you use the REST API method to check will see the data changes, /api/v1/courses/67346/modules?include[]=items

[seanbeirnes]

Hello @PhillipJacobs,

It is entirely possible that Canvas is caching the GraphQL queries in Redis on the backend. I also know that Canvas uses Apollo for caching GraphQL queries on the client side too.

[PhillipJacobs]

Thank you Sean!

What I expect is happening as well. The back end is my main concern so can know how out of date the info may be. Maybe someone from Instructure side will see this and confirm 🙂

-Phil