adayush opened a new issue, #40047:
URL: https://github.com/apache/superset/issues/40047
### Bug description
Hi team,
We have been facing a issue where the Reports are not being completed or
failed, they are just stuck in sending state (attached screenshot below).
## Observations:
1. Both existing and new reports have this issue
2. We tried using both CSV & PNG & PDF reports sent to Email
3. Worker logs (before setting reports to Error state) just mention that
`Report Schedule is still working, refusing to re-compute`
4. After we set all reports to Error state -> Worker logs have nothing
useful. We don't get **any** logs after the one saying report is triggered
(logs shared below). So report is visibly stuck in sending state
```
[2026-05-12 10:05:00,003: INFO/MainProcess] Task
reports.scheduler[1daef3b7-ebb2-4f85-991e-245b1991f363] received
[2026-05-12 10:05:00,020: INFO/ForkPoolWorker-1] Scheduling alert New Design
BI plans. eta: 2026-05-12 10:05:00
[2026-05-12 10:05:00,026: INFO/MainProcess] Task
reports.execute[fea367b7-33f8-4ce9-aeda-c108457ae169] received
[2026-05-12 10:05:00,027: INFO/ForkPoolWorker-2] Executing alert/report,
task id: fea367b7-33f8-4ce9-aeda-c108457ae169, scheduled_dttm:
2026-05-12T10:05:00
[2026-05-12 10:05:00,028: INFO/ForkPoolWorker-2] session is validated: id
17, executionid: fea367b7-33f8-4ce9-aeda-c108457ae169
[2026-05-12 10:05:00,052: INFO/ForkPoolWorker-1] Task
reports.scheduler[1daef3b7-ebb2-4f85-991e-245b1991f363] succeeded in
0.04761948483064771s: None
[2026-05-12 10:05:00,210: INFO/ForkPoolWorker-2] Running report schedule
fea367b7-33f8-4ce9-aeda-c108457ae169 as user sharpsell-admin
[2026-05-12 10:05:00,334: WARNING/ForkPoolWorker-2] A downstream warning
occurred while generating a report: fea367b7-33f8-4ce9-aeda-c108457ae169.
Report Schedule is still working, refusing to re-compute.
Traceback (most recent call last):
File "/app/superset/tasks/scheduler.py", line 99, in execute
).run()
^^^^^
File "/app/superset/utils/decorators.py", line 266, in wrapped
return on_error(ex)
^^^^^^^^^^^^
File "/app/superset/utils/decorators.py", line 236, in on_error
raise ex
File "/app/superset/utils/decorators.py", line 259, in wrapped
result = func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/app/superset/commands/report/execute.py", line 896, in run
).run()
^^^^^
File "/app/superset/utils/decorators.py", line 266, in wrapped
return on_error(ex)
^^^^^^^^^^^^
File "/app/superset/utils/decorators.py", line 236, in on_error
raise ex
File "/app/superset/utils/decorators.py", line 259, in wrapped
result = func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/app/superset/commands/report/execute.py", line 858, in run
).next()
^^^^^^
File "/app/superset/commands/report/execute.py", line 783, in next
raise exception_working
superset.commands.report.exceptions.ReportSchedulePreviousWorkingError:
Report Schedule is still working, refusing to re-compute.
[2026-05-12 10:05:00,341: INFO/ForkPoolWorker-2] Task
reports.execute[fea367b7-33f8-4ce9-aeda-c108457ae169] succeeded in
0.31424060883000493s: None
```
## Here's what we've tried so far, but didn't help:
1. Marking all reports being in "Working" state to "Error" state using SQL
query
2. Also tried marking them to "Not triggered"
3. Rebuilt superset image and restarted worker
4. Increased celery worker timeout in config from 1 minute to 5 minutes
### Screenshots/recordings
<img width="1533" height="508" alt="Image"
src="https://github.com/user-attachments/assets/b6dbdcd6-674c-4adb-ba1c-42d6d8e51986";
/>
### Superset version
5.0.0
### Python version
3.9
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to
my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug
report.
- [x] I have checked Superset's logs for errors and if I found a relevant
Python stacktrace, I included it here as text in the "additional context"
section.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
