You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Unabled to create Subscriptions with schedule as "On Extract Refresh" #1658
Subscriptions can be created on specific schedules. However, it is not possible to create subscriptions based on extract refresh. The SubscriptionItem class (subject, schedule_id, user_id, target) requires schedule_id as a mandatory parameter, so it cannot be ignored or set to None.
I have read some articles to ignore/ dont pass "schedule_id" but it doesn't seems to be working.
Env:
Tableau Server: On Prem: 2025.1.1 (20251.25.0415.1018) 64-bit Windows
Python version: 3.12.0
TSC library version: 0.38.
To Reproduce
Try to create a subcription that should have schedule as "On Extract Refresh"
Results Error When None is passed to Scheduled ID: new_sub = TSC.SubscriptionItem(email_subject, schedule_id=None, user_id, target)
INFO Creating a subscription (<Subscription subject(Test_User_TestSubscriptions2_withoutschedule) schedule_id(None) user_id(f57ca8cb-4a14-4b01-ac7b-721ffe260537) target(<Target#761209c1-decd-4626-8bbb-7be632e2efe8, view>))
Failed to create subscription. below is the error message
INFO cannot serialize None (type NoneType)
Error When Schedule_Id parameter is skipped: new_sub = TSC.SubscriptionItem(email_subject, user_id, target)
SubscriptionItem.init() missing 1 required positional argument: 'schedule_id'
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.
Activity
jorwoods commentedon Oct 6, 2025
At current, I do not believe there is server side support for creating "on extract" subscriptions via the REST API.
github-actions commentedon Jul 24, 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.
fixup: use existing 'Server-Side Enhancement' label instead of new one
github-actions commentedon Aug 8, 2026
Closing due to inactivity. If this is still relevant, please reopen or file a new issue.
Drop On Extract Refresh entry, soften intro and daily-schedule wording
docs: add Known server-side limitations section to api-ref.md (#1842)
ci: exempt Server-Side Enhancement label from stale bot (#1841)
samples: credential helper, pagination fixes, and new jobs/subscripti…