Skip to main content
Bulk Actions allow users to apply a consistent operation to multiple items simultaneously rather than updating each individually, selecting grouped assets and using Assist to execute sweeping changes in seconds. Bulk Actions connects several parts of LILT, allowing you to trigger changes and monitor progress asynchronously without needing to remain in your original Assist conversation.
  • Context Database Selection Bar: Displays the total count of your selected search results and the corresponding text prompt where you describe the desired change.
  • Assist Plan Card: Submitting your prompt opens a side tab displaying the staged plan card for review. Once you run the plan, the selection is automatically cleared and the side tab closes.
  • Bulk Actions Tray: A collapsible tracker that appears while background work is active. It shows real-time progress and provides immediate controls to pause, resume, or stop the task.
  • Bulk Actions List Page: A broader dashboard that groups all historical and ongoing actions into Active, Completed, and All tabs, displaying overarching statuses, progress bars, and task controls.
  • Action Details Page: Accessible from the List Page, this deep-dive view shows detailed progress for a specific action, grouped failure states, and an item-level execution log complete with CSV export options.

​
How it Works

​
1. Select the items

Bulk Actions operate on a selection attached to an Assist conversation.
  • To start, use the Context Database’s unified search and filtering to find your target data.
  • Select specific items or group multiple results together (excluding any individually deselected items).
  • This selection defines the strict scope of the action; the LILT Agent will not modify items outside of this attached selection.

​
2. Describe the change

Use the prompt field to request a single, consistent operation to apply across the selection. Examples:
  • “Replace ‘v4’ with ‘v5’ in the target of every selected termbase entry.”
  • “Archive all selected jobs.”
  • “Set the custom property region to EMEA on every selected project.”
Note: Assist translates the request into a supported rule or action. Ambiguous requests, unsupported actions, or changes requiring individual editorial judgment will be refused rather than approximated.

​
3. Review the staged plan

Preparing a plan does not execute the change. Assist will generate a plan card detailing:
  • The specific action to be taken.
  • The affected-item count and selection/search scope.
  • Sample item references.
  • Counts for skipped or rejected items.
  • An estimated processing time.
Review the counts carefully, as invalid results may be rejected and items that require no changes will be skipped. If no items qualify for the change, Assist will return a “nothing to change” message without generating a runnable plan.

​
4. Run the action

Click Run action to submit the staged plan and initiate execution.
  • The explicit button click—not the initial conversational prompt—starts the process.
  • Staging a newer plan within the same conversation automatically supersedes older open plans.
  • Draft plans expire by default after one hour.

​
Supported Assist Actions

Note: While Context DB allows you to search and view many data types (like Segments, Style Guides, and TMs), Assist Bulk Actions are currently only supported for the items listed below.
Item TypeSupported Operations
Termbase EntriesSet target text, find-and-replace, regex replacement, change capitalization, and delete entries.

(Source-term edits and judgment-based rewriting are not supported).
DocumentsMark the current workflow stage complete, or move documents to a specified numeric workflow-stage ID.
JobsRename, update due dates, archive, restore/unarchive, and deliver.
ProjectsRename, update due dates or project names, archive/unarchive, deliver, and set or remove custom properties.
Resources / Data SourcesExport in supported TMX formats, termbase CSV formats, or the resource’s native format.
(Note: If an operation is available elsewhere in LILT, it is not automatically supported through Assist Bulk Actions. Only the implemented action types above are supported.)

​
Monitoring, Limits, and Recovery

Asynchronous Execution: Once submitted, actions run safely in the background. Depending on task state, you can use the tray or list pages to pause, resume, cancel, or retry execution. Submission Limits: By default, submissions are capped at 5,000 items (this limit may vary based on deployment configuration). Cancellation vs. Rollback: Canceling an action is not a rollback. Tasks that are already actively running may still finish after a cancellation command is sent. Undo Functionality: Where supported, triggering an undo creates a completely new submission that restores the values captured when the original plan was prepared.
  • Undo applies only to successfully completed tasks with valid undo instructions.
  • The original work must be fully finished before an undo can be initiated.
  • Undo is only available to the original task owner.
  • Caution: Using undo will overwrite any manual changes made to the items after the original plan was prepared.

​
Relationship to Standard Bulk Controls

LILT continues to provide separate bulk controls within its standard user interface:
  • Project Selections: Support actions such as edit, deliver, archive/unarchive, auto-assign, and delete (availability depends on the current states of all selected projects).
  • Document Controls: Include assignment, pretranslation, deletion, assignment acceptance/rejection, and marking work done (subject to user permissions and workflow eligibility).