Repository navigation
[Type 1] Implement Tableau Cloud-specific requests for the Subscriptions endpoint #1373
Description
Description:
The Subscriptions endpoint works somewhat differently for Tableau Cloud & Tableau Server, in that the subscription schedule needs to be defined as part of the request for Tableau Cloud. As of now, TSC only supports the request format for the Server endpoint, where a schedule id needs to be provided. This feature would implement the Tableau Cloud request format alongside the Tableau Server format. The subscriptions REST API documentation: https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_ref_subscriptions.htm#tableau-cloud-request
A "quick-and-dirty" implementation could allow the user to specify in the SubscriptionItem definition that instead of schedule_id, they'd like to set all the Tableau Cloud-specific fields. However, if it is expected that more API methods will have Tableau Server & Cloud versions, it could be beneficial to automatically detect Tableau Cloud vs Tableau Server during the construction of the Server object and pick the correct endpoint specs accordingly. TSC doesn't currently seem to have a way to distinguish between requests made to Tableau Cloud & Tableau Server, so this would need to be added first, potentially by checking the server URL for (online.tableau.com).
Activity
[-][Type 1] Implement Tableau Cloud-specific requests in the Subscriptions endpoint[/-][+][Type 1] Implement Tableau Cloud-specific requests for the Subscriptions endpoint[/+]CodingOnWindowsOS commentedon Dec 14, 2024
Any news on this? I seem to have stumbled upon the same issue. It works well on my Tableau Server instance but not on my Cloud instance. It appears the create and update methods of the subscriptions endpoint do not work for Tableau Cloud in the same way they work on the front-end when performing the task manually.
github-actions commentedon Jul 28, 2026
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. If this is still relevant, please comment to keep it open.
github-actions commentedon Sep 30, 2026
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. If this is still relevant, please comment to keep it open.
github-actions commentedon Oct 15, 2026
Closing due to inactivity. If this is still relevant, please reopen or file a new issue.