Skip to content

3rd party API call results get cached on Gitbook's side #795

@vincentderidder

Description

@vincentderidder

Context:
I'm creating an Integration that fetches data from an API to display in a block on a Gitbook page with ContentKit

Problem:
Old data keeps getting displayed, even after removing the integration completely and re-adding it. I suspect this is because Gitbook application caches the API calls en returns the cached result.

What I've tried
Cache-Control on the API call set to no-cache
Disabled the element cache with element.setCache({ maxAge: 0 });

Example:
The Linear Integration faces the same issue. When adding a ticket to a page, the data does not update after changing it in Linear.
Even after clearing local cache, trying a different browser or device

Expected behavior:
We can set the cache maxAge and it gets respected by the Gitbook application so no old data gets shown.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions