Skip to content

Why a Record Cannot Be Edited Right Now

A run owns the Task, your role does not allow it, the quota is used up, or the Task has expired: what each looks like and what to do.

Draft brief for authors. Replace with the final text; keep the structure.

Page type: Reference · Audience: Business user

Contains: a running, paused or scheduled run owns the Task (edits and deletes answer with a message; wait, or stop the run under Background Jobs); your role allows viewing only; the add-on's quota is used up (editing still works, processing does not); the Task expired; a Successful record is never changed by Mass Edit.

Related information: pause-resume-stop, authorization-model, messages-staging.

Source in the product repository: srv/lib/active-run-guard.js (D49).

Last updated: