41258 backend [workflows] Delete outdated workflows api response data

[andrey-usov]

Problem

Workflow and task responses carry fields that no client uses. They inflate every response,
make the API harder to maintain and slow down any further change in this area.

Fix / Solution

• Workflow.status_updated — removed the model field, the save() override that kept it
  up to date, and everything that read it: TemplateQuerySet.workflows_updated_from,
  workflows_updated_to, avg_workflow_duration and the WorkflowDurationFilter /
  WorkflowSuccessRateFilter filtersets, which were not attached to any view. Migration
  0260_remove_workflow_status_updated.

Not in this PR: task.is_completed. The task asks to drop it and derive the value from
performers, but that is not possible for group performers: when a group member completes his
part under require_completion_by_all, the completion is stored in a hidden GROUP_USER row,
and performers only exposes user and group rows. The item was cancelled after review, the
field and its tests are restored in c665670c.

Not in this PR: workflow-level due_date_tsp. The process-page widget is hidden, but the
progress bar and public GET/webhooks still read the field. Moved to a follow-up; restored in
9d63d4a1.

Not changed: input serializers (WorkflowCreateSerializer, WorkflowUpdateSerializer),
filter serializers (TaskListFilterSerializer), event serializers (SubWorkflowEventSerializer,
TaskEventJsonSerializer), raw SQL queries.

Release notes

No user-facing changes. An unused internal workflow timestamp has been removed from the
database. Workflow and task due dates in API responses are unchanged.

Changes

API:

• Workflow.status_updated dropped from the database
• GET /workflows, GET /workflows/:id, PATCH/run responses and workflow webhooks keep
  due_date_tsp
• GET /v2/tasks/:id keeps top-level is_completed

Web-client: No changes.

Test cases

API:

Authorization	Test case	Expected result
Account owner	GET /workflows	due_date_tsp still present
Account owner	GET /workflows/:id	due_date_tsp still present
Account owner	PATCH /workflows/:id with due_date_tsp	Accepts input, saves to model, response contains due_date_tsp
Account owner	POST /templates/:id/run with due_date_tsp	Accepts input, saves to model, response contains due_date_tsp
Account owner	GET /v2/tasks/:id	is_completed still present at top level and true after the user completed his part of a require_completion_by_all task
Account owner	GET /v2/tasks/:id	sub_workflows, performers[].is_completed and task-level due_date_tsp still present
Account owner	Workflow started webhook	Payload still contains due_date_tsp
Account owner	Task completed webhook	due_date_tsp present on nested workflow, is_completed still present at task level
Account owner	Any workflow status change	Status changes are applied, no error from the removed status_updated column

Web-client: No changes — no test cases.

Made with Cursor

Note

Remove status_updated field and related workflow duration/success-rate filters

• Removes the status_updated DateTimeField from the Workflow model via 0260_remove_workflow_status_updated.py and drops the save override that maintained it
• Deletes WorkflowDurationFilter and WorkflowSuccessRateFilter from filters.py, which exposed date_from/date_to filters backed by workflows_updated_from/workflows_updated_to\n- Removes workflows_updated_from, workflows_updated_to, and avg_workflow_duration from querysets.py since they depended on workflows__status_updated
• Updates tests, fixtures, and the workflow creation path in workflow.py to stop referencing status_updated
• Risk: any out-of-tree code importing Workflow.status_updated, WorkflowDurationFilter, WorkflowSuccessRateFilter, or the three deleted TemplateQuerySet methods will fail; in-tree callers are already cleaned up

^{Macroscope summarized 9d63d4a.}

[cursor]

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.

[pneumojoseph]

@andrey-usov Workflow.status_updated is used ?

[andrey-usov]

@pneumojoseph No, it's dead. The field is written on every status change, but the only
readers are workflows_updated_from / workflows_updated_to / avg_workflow_duration
in querysets.py, and those are called only from WorkflowDurationFilter and
WorkflowSuccessRateFilter — two filter sets that aren't attached to any view. It was
never in API responses either.

Removed the field, the dead filters and added migration 0259. Tests are green.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 1ab8f3f. Configure here.}