World export fails - get_id

Open
Feature
API
Reported by
Patrick-M
Opened
Assigned to
SoulLink
Last activity

Description

  • Scenario: go to a world > Advanced Settings > Export World > Export this world
  • Next screen: I put my API token
  • Next screen: I click on start
  • => nothing happens. refresh, click on the big "Reset" button, then "Start" again =>   Error message : An error occurred while scheduling the export: 'Job' object has no attribute 'get_id'   This could mean that one of my articles has a bad idea. No problem to go and even delete and rebuild it... but which one among the hundreds of articles?

    Steps to Reproduce

  • Scenario: go to a world > Advanced Settings > Export World > Export this world
  • Next screen: I put my API token
  • Next screen: I click on start
  • => nothing happens
  • Refresh page (F5)
  • Click on the big "Reset" button
  • Click on "Start" again
  • => Error message : An error occurred while scheduling the export: 'Job' object has no attribute 'get_id'

    History

    Comments and updates to this report

    Patrick-M
    I comment on my own bug I just filled:  
  • After submitting the bug, I had the idea to go to a private browing session to https://toolbox2.worldanvil.com/
  • I put my API key
  • And there, I see the 2 tries of succeded export programmed (which seemed in error because of the get_id error), ready to be downloaded, with success.
  • The bug is still to be opened: even though the trigger of export worked, the workflow of the job in the https://toolbox2.worldanvil.com/ interface did not. And it can be a trap to "retry a lot of times" thinking it does nothing but in reality, it triggers the real work each time.
    Syarx Developer
    Assigned SoulLink
    SoulLink Assignee
    Yeah the UI is a bit janky like that. There is however currently a bug that prevents the export from working properly, as it stops at the images. Though it does export articles and categories, so if you have mostly those then you might not notice.
    Chanther

    Experiencing the same issue on Mac using Chrome, with the same error message: An error occurred while scheduling the export: 'Job' object has no attribute 'get_id'

    Further steps:

    • Attempted to Refresh the World Index - had no effect on the export error.
    • Excluding image metadata from the export did not produce any change in the export error.
    • Excluding every export category except articles did not produce any change in the export error.

    I have two worlds - experiencing the error identically on both.

    ProfPorterfield
    I am experiencing the exact same problem in the exact same way and have also tried all of the attempted "fixes" above. No luck here either.
    ss2020

    I am not able to download anything, not even just articles.

    I am expereincing this problem with 2 of my worlds while only trying to download articles.

    Chanther
    As an update - though I am still getting the same error message, after a while a successful export does appear and I can download it without issue. (And because I tried many times, I ended up with 10 or so exports.)
    Toby R. Beeny

    Was having the same issue. Got a download despite the error however. I ran the zip through AI to validate the contents and they were all intact, except for the images and maps. The zip file still points to them but they are not present, so there is still an actual export failure happening.

    CRFC11
    Also having the same issue as above just getting

    An error occurred while scheduling the export: 'Job' object has no attribute 'get_id'
    id8tionist
    Also getting the error....
    Empireo

    I have the same issue and tried similar steps to those described above

    Empireo

    As OP suggested: Opening the tool in a private tab shows the previous export attempts. And a download was succesfull. Attempting to do a new backup still shows the same error but reloading that page then shows you a new export.

    Beric
    I have been in need of a fix to this for over a month, now. Unlike others, simply waiting has not helped.
    TotallyNotAWizard

    Same.... all three of my worlds will not export.

    Hadessian

    Same issue, nothing seems to help. :c

    Janner
    Same issue.
    Pandora9
    I am also having the same issue.
    Smorholm

    doesnt work for me either.

    irpguardian
    Just tried this myself and get the same issue.
    "An error occurred while scheduling the export: 'Job' object has no attribute 'get_id' "
    Dreik
    This is getting really bothersome. I just bought a yearly membership just to get access to the export feature...
    Redevil387

    I have this issue.

    Thootjuh
    I also have this issue
    palosandro
    I have the same issue, and this is really annoying since exporting is a fundamental part of my world building flow.
    Illuvatar118

    Same issue here. I even tried to only export Articles/Secrets and it still failed. Any resolution?

    GlJonny

    I am experiencing the same issue. Using Windows with Firefox. I wanted to cancel my subscription, because I stopped playing. I cant cancel, until I back-uped my world, but I am also not willing to pay for the sake of a bug happening.

    Please fix this issue ASAP! :(

    G_C

    Same - very annoying, and this is a key feature for me.

    FJ Brodie
    I am also experiencing this, and I have tried various browsers and both Linux and Android, even though it seems a server-side error.   In my case, the exports fail or partially succeed. In the latter sense, I get some of the articles, but not manuscripts or prose. I'll run it again and see what happens, though multiple requests can cause jobs to "overlap" and interrupt each other. So, error or no error, I will run it once and check back tomorrow to see the result.
    WatchAndWarrant

    Experiencing this issue as well. I was experiencing partially failed exports back in June and figured I was just doing something wrong.

    Now, it seems clear that it's a part of a bigger problem with the exporter.

    The platform will loose good will over this if people can't export their data out of the WA db.... this needs to function. Even if things aren't organized properly, there still needs to be a method of getting or worlds out of WA.

    braskey

    I have this issue, too. Opening in a private tab did not work for me.

    ninjametimbers
    This bug is blocking my workflow. I've tried different browsers, private windows, resetting the API token, and nothing works. I am still getting the 'Job' object has no attribute 'get_id' error. I was getting it a month or two ago and I still managed to get a download for the exported world, but this time
    armature arcana

    Just chiming in to say experiencing the same error. Private browsing exposed the failed exports for download. JSONs and HTMLs came through fine, but no images.

    Not sure if it's relevant, but the world is private and in draft mode.

    irpguardian
    To further dive into this (still unfixed) issue to hopefully shed some light on what's happening.
    On 30 October, I did several "exports" on my world, with the typical get_id error we all know and love. However, coming back to it today (2 Nov) I saw there was about 5 different "exports" available.
    While the preview on the google-docs page is mostly useless as it only shows up to 199 items (I have over 700 articles already), I downloaded a few of the exports and found that some had more data than others. And while not comprehensive in what they should have (which is everything) patched together they have a more significant amount.
    So my next test would be to individually select only 1 of each of the export fields and see if each individual of those gets fully populated. A painful workaround for now, until this matter is resolved.
    Uruschk
    I was having this issue a month ago and I am still having this issue now in November. I am not able to export anything, not even when I select only articles. I've tried with HTML toggled on or off, flattening toggled on or off, tried in private mode, no luck. I see a very long list of people reporting the same issue, but not a single update or comment from a developer or assignee since August 5th. It appears we are calling into a howling void.