Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Identifying suspended extract refresh failures #41

Closed
arunyadav19 opened this issue May 13, 2020 · 5 comments
Closed

Identifying suspended extract refresh failures #41

arunyadav19 opened this issue May 13, 2020 · 5 comments
Labels
enhancement New feature or request

Comments

@arunyadav19
Copy link

Sir,

Is there any way we can identify LUID's or some other way to identify those extract refresh schedules which are in suspended state so that they can be removed.Instead of deleting the schedule ( which might be used by other users as well) , I would remove the individual extract refresh task set on that particular workbook.

Reason behind doing this is: To reduce the error failure rate in an extract heavy environment.
@mcoles
Copy link
Contributor

mcoles commented May 14, 2020

Right now, using TS Background Tasks, the only way would likely be to use the Notes field to look for "suspended", and the grab the workbook/data source LUID, and track down the appropriate Task LUID via the REST API. But, we should add a few things to TS Background Tasks to make this easier:

Add Task LUID
Add consecutive failure count
Add "suspend_state" field from any item tables it exists in (just data_alerts and metrics at this time..this may have to be done carefully, as having it NULL for more popular items, such as workbooks and data sources could be pretty confusing)

@mcoles mcoles added the enhancement New feature or request label May 14, 2020
@arunyadav19
Copy link
Author

Screenshot 2020-05-15 at 4 26 22 PM

Not sure if my screenshot is visible . I used TS Background Tasks ( big Thanks to you for all these data sources) , used this column "Job LUID" to get Luid's of these suspended tasks and copied all these luid's in a excel sheet.

Then used this below mentioned code to remove these failed extract schedules by providing these LUID's but it did not work. It

url1 = "https://tableauserver.com/api/3.7/sites/siteid/tasks/extractRefreshes/"
url2=url1+cell
response = requests.request("DELETE", url2,headers=headers, data = payload)

@arunyadav19
Copy link
Author

Looks like I'm missing something or not looking at right place. Would you mind sharing a solution working for you ?

@mcoles
Copy link
Contributor

mcoles commented May 18, 2020

Job LUID is different than Task LUID. That's why I was saying I think you'd have to get the actual Item LUID for the workbook/data source, then obtain the Task LUIDs based on those.

mcoles added a commit that referenced this issue Oct 1, 2021
@mcoles
• All / Multiple:
543be1a 
	Added metadata on Collections (TS Content, TS Events, TS Users) #53
	Added metadata on Metrics (TS Content, TS Events, TS Users, TS Background Tasks) #33
	Incorporate new Web Authoring event into added in 2021.1 (TS Content, TS Events, TS Users) #59
	Updated "Site Role" with improved logic (with thanks to @thechadd) #30
	Version field updated to 03.01

•	TS Events
	Added "details" field #57
	Refactored Historical Item Revision for consistency (should now match revision history from UI) #58

•	TS Content
	Fixed error in "User Filter" calculation #51
	Added projects as top-level item type #4
	Add extract encryption status field #35
	Add "controlled_permissions_enabled" field #19
	Add data_engine_extracts field for Flows #36
	Expanded "access counts" to include a broader set of interactions (web edit, download, export)

•	TS Web Requests
	Fixed incorrect Duration for requests (no longer rounds, and precision increased to milliseconds--thanks to @rk2511) #56

•	TS Background Tasks
	Improved Data Alerts information and added several fields, populated hyperlinks #39
	Added field "Increment Date" that should be used for incremental refreshes, with field "Is Max Record" added as a data source filter.
	Added job creator information #24
	Account for "Cancelled" tasks #32
	Identifying suspended extract refresh failures #41
	Fixed Item Owner info for subscriptions #48
@mcoles mcoles mentioned this issue Oct 1, 2021
Merged
@mcoles mcoles closed this as completed Oct 1, 2021
@mcoles
Copy link
Contributor

mcoles commented Dec 1, 2021

This was added as the field named "Task State"--just in case anyone was looking for "Is Suspended", and not finding it...like I was for the last half hour, despite being the one who added it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mcoles @arunyadav19