Currently, the Contentful API for fetching entry schedules does not support providing a specific list of entry IDs to retrieve schedules only for those entries. Instead, the API fetches all scheduled actions for the entire Contentful space.
This limitation introduces inefficiencies, particularly in large spaces with numerous scheduled actions, as it requires additional processing on the client-side to filter the results for specific entries and paginate requests to Contentful. For projects with high-volume content, this behavior significantly impacts performance and usability.
There is a need to support in filter for sys.id in schedule search https://www.contentful.com/developers/docs/references/content-management-api/#/reference/scheduled-actions/scheduled-actions-collection/get-all-scheduled-actions-of-an-entry/console/js
In this case we can use the sdk as following:
client.getSpace('<space_id>')
.then((space) => space.getScheduledActions({
'environment.sys.id': '<environment_id>',
'sys.status': 'scheduled',
'sys.id[in]': 'id1, id2'
}))
Currently, the Contentful API for fetching entry schedules does not support providing a specific list of entry IDs to retrieve schedules only for those entries. Instead, the API fetches all scheduled actions for the entire Contentful space.
This limitation introduces inefficiencies, particularly in large spaces with numerous scheduled actions, as it requires additional processing on the client-side to filter the results for specific entries and paginate requests to Contentful. For projects with high-volume content, this behavior significantly impacts performance and usability.
There is a need to support
infilter forsys.idin schedule search https://www.contentful.com/developers/docs/references/content-management-api/#/reference/scheduled-actions/scheduled-actions-collection/get-all-scheduled-actions-of-an-entry/console/jsIn this case we can use the sdk as following: