"Job Status" dialog keeps popping up

[autodesk4AYMR]

I exported a file as STL about 3 weeks ago. The Job Status dialog, which is modal, popped up with the status when it was completed. I closed it. But then half an hour later it popped up again. And basically ever since then it pops up randomly about 25 times per day, every day, if Fusion 360 is open. This seems like a bug. It's kind of annoying bc I have my Windows task bar minimized and this modal dialog unminimizes it. Make it stop plz.

[Phil.E · Accepted solution]

Try this: Help > Support and Diagnostics > Clear Cache Data. Does this help?

[don9ZUEA]

Hi,

Yes, it worked for me clearing the cache.  Still we should be able to clear the job status for all completed jobs and not have to perform this work-around each time a job is initiated.

Cheers,

Don

[phil_eichmiller]

Can you list the steps required to trigger this issue? It's not commonly reported and in order to debug it we need to reproduce it.

[don9ZUEA]

Easy to reproduce:

1. Open any simple project with a body (mine included a relatively
simple wheel hub with a section analysis:
2.
3. Export the project as an STL file type (I haven't exported to other
types but I assume the same thing will occur). The job status dialog pops
up
4.
5. Once the job is complete, close the dialog
6. Wait for a while and that annoying dialog will pop back up. It does
take a while and could be related to the computer going into sleep mode
during the interim. Which I've just tested and yes, the dialog will appear
once the computer comes out of sleep mode. If the job(s) are complete there
is no need to display the job status dialog

Cheers,



Don

[andyvincentuk]

Also getting this so it is still an (annoying!) issue

[velvetrevolution]

I am also getting this problem after an export, in my case to a SKP format.

[Phil.E]

Does clearing your cache help?

[velvetrevolution]

Yes that worked, thanks. After I found it. Not the easiest thing to find
but now I know.

[barnabas]

This also happens to me on M1 Macbook Pro. Dialog box for export continually pops up. I've cleared cache and will see if this helps.

[barnabas]

I cleared the cache and now Fusion360 crashes when attempting to launch.

[Phil.E]

Hi,

Sorry to hear this. In this case, the Job Status problem originally reported in 2020 is not the same problem.  Thanks for sending the crash report.

Can you try the service utility, "repair" option?

https://knowledge.autodesk.com/support/fusion-360/troubleshooting/caas/sfdcarticles/sfdcarticles/Ove...

[qsimon]

Can confirm I exported to .stp and am having the same issue. It was literally a single sheet metal body. The dialog box is reappearing almost once/minute for me.

[Jwmachinefab]

I have also been having this job status pop up constantly. I tried to clear the cache and it did not help. I have updated the fusion as well and nothing seems to help. 

[ulrich.jelinek]

I also have this pop-up. I notice that this seems to be unresolved for years now.

The job status window (with all jobs listed as 'complete') appears every time the computer awakes from sleep mode. Every time I close it either with the 'close' button or with the 'x' and every time it is there again when I'm back from a break. It started the day after I have exported a complete model as  f3z file.  Fortunately, saving a body as STL does not trigger it. Will try to clear the cache now, but this is not a valid solutiion in my opinion.

I encountered this intrusive job  status window several times in the past (don't remember whiche file type exactly I had exported then), and it stopped reappearing after several days all by itself without any actions from my side.

- Ulrich

[Phil.E]

Have you tried clearing local cache? 

https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/How-to-clear-local...

[PaulCurtis]

I am seeing the same issue. The trigger was attempting to export a model as a dxf file. Fusion crashed when I attempted to clear the cache. The pop up appears after I wake my computer up after a sleep/hibernate. Not sure which one.

[Phil.E]

Did you try manually clearing cache? Article.

[PaulCurtis]

Yes clearing the cache (which restarted the app) cleared the issue. Hard
to tell if it was restarting the app or clearing the cache that fixed
things.


Paul

[Phil.E]

Thanks for the confirmation. This issue was more common previously, but can obviously still happen in some circumstances. If we see more reports like this a fresh investigation will be opened.