mirror of
https://github.com/chatwoot/chatwoot.git
synced 2026-06-04 21:02:35 +08:00
f27bbef73b
## Summary One-off SMS and WhatsApp campaigns now show a `Processing` state while the audience send is in progress. The campaign moves to `Completed` after processing finishes, and already-processing campaigns are skipped by the scheduler to avoid duplicate sends. ## Closes - [CW-6037: feat: Introduce an in-progress status for campaigns](https://linear.app/chatwoot/issue/CW-6037/feat-introduce-an-in-progress-status-for-campaigns) ## Screenshot SMS campaign card showing the new `Processing` status. <img width="3840" height="2160" alt="framed-campaign-processing-status" src="https://github.com/user-attachments/assets/de7913b5-65fb-4121-9034-24a568eb0382" /> ## What changed - Added `processing` as a campaign status. - Mark one-off campaigns as `processing` under a row lock before the send service runs. - Complete SMS, Twilio SMS, and WhatsApp one-off campaigns after audience processing finishes. - Keep campaigns in `processing` if an unexpected service error escapes, so the scheduler does not automatically resend the audience. - Added the `Processing` label for SMS and WhatsApp campaign cards. ## Known operational behavior If a worker is interrupted or an unexpected service error escapes after a campaign is marked `processing`, the campaign can remain in `processing`. This is intentional for now to avoid automatic full-audience resends. Installation admins can decide whether to mark the campaign completed or restart it manually from the Rails console after checking what was sent. ## How to test - Create a one-off SMS or WhatsApp campaign scheduled for now. - Run the scheduled job or trigger the campaign job. - Confirm the campaign card shows `Processing` while the audience is being processed. For small audiences, refresh during processing or use a larger audience so the state is observable. - Confirm the campaign moves to `Completed` after audience processing finishes. - Confirm an already-processing campaign is not enqueued again by the scheduled job. |
||
|---|---|---|
| .. | ||
| account | ||
| agent_bots | ||
| agents | ||
| auto_assignment | ||
| avatar | ||
| campaigns | ||
| channels | ||
| contacts | ||
| conversations | ||
| crm | ||
| inboxes | ||
| internal | ||
| labels | ||
| migration | ||
| notification | ||
| webhooks | ||
| bulk_actions_job_spec.rb | ||
| conversation_reply_email_job_spec.rb | ||
| data_import_job_spec.rb | ||
| delete_object_job_spec.rb | ||
| event_dispatcher_job_spec.rb | ||
| hook_job_spec.rb | ||
| mutex_application_job_spec.rb | ||
| send_on_slack_job_spec.rb | ||
| send_reply_job_spec.rb | ||
| slack_unfurl_job_spec.rb | ||
| trigger_scheduled_items_job_spec.rb | ||
| update_slack_message_job_spec.rb | ||
| webhook_job_spec.rb | ||