This seems to be a Python AttributeError that occurs while the export is being scheduled as a background job, before any world data is processed. This suggests a problem on the server side rather than with my world's content or structure. My assumption (not verified) is that the job queue library, for example RQ (Redis Queue), was updated, and the export code still calls the old job.get_id() method instead of the job.id attribute. If that is the cause, replacing get_id() with id in the export scheduling code should fix it.
I also found an existing tracker entry, "World Export not working on all worlds". It may be related, but I can't confirm that it shows the same error.
Could you please check whether the export service or its dependencies were recently updated? Thank you!