Skip to content

Error code 409093 should not result in an error but a warning message alone #1090

Closed

Description

@Sairam90

Describe the bug
Error code 409093 -which indicates that the workbook/datasource is already queued for refresh must simply result in a message that refresh is queued and not in a error

Versions
Details of your environment, including:

  • tableauserverclient == 0.18.0
  • Python version 3.8.10
  • TSC library version

To Reproduce
Refresh a workbook while a refresh is not complete

Results
What are the results or error messages received?
409093: Resource Conflict
Job for <workbook/datasource> is already queued. Not queuing a duplicate.
NOTE: Be careful not to post user names, passwords, auth tokens or any other private or sensitive information.

Activity

  1. jacalata commented on Aug 16, 2022

    @jacalata
    Contributor

    Good call, should be fixed.

  2. Sairam90 commented on Sep 8, 2022

    @Sairam90
    Author

    Is it possible to get the previous job_id for a particular workbook .. else I cannot query it's status and avoid the above error

  3. jsuap commented on Jan 13, 2023

    @jsuap

    Is it possible to get the previous job_id for a particular workbook .. else I cannot query it's status and avoid the above error

    I would like this as well

  4. ok-jaime commented on Oct 8, 2023

    @ok-jaime

    would really love this fixed and also a way to be told what the job Id is for the resource conflict. I seem to be getting this error on initial queueing I do so hoping we can get something that helps in auditing server response.

  5. rpappu87 commented on Jan 19, 2024

    @rpappu87

    was this fixed? I still get the same error and not warning.

  6. DStoilov96 commented on Mar 26, 2024

    @DStoilov96

    I second that this should me a message and not an error .

  7. haythamsoufi commented on Jul 24, 2024

    @haythamsoufi

    Has this issue been fixed? I'm still encountering it now and it's annoying

  8. added a commit that references this issue on Apr 6, 2026
  9. added 2 commits that reference this issue on Jun 18, 2026
    4bc913d
    76f2753
  10. added a commit that references this issue on Jun 20, 2026
    368cee4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions