Manual execution

You can manually run automations on existing object sets. This is useful for backfilling data or testing automations before a wider release.

Manual executions are considered run by the user who selects Execute in the Automate interface. Users must have Compass edit permissions on the Automate resource to manually execute an automation.

To manually execute an automation, first create a new automation with the desired effects. Then, open the automation and navigate to the Execute tab.

When an automation is manually executed, configured effects for that automation will be triggered immediately (optionally for a user-defined object set, depending on the condition).

Example: Remediate with manual execution

Large backlogs may cause snapshot expiration errors during manual execution. To work around this, use a function-backed object set to process the backlog in manageable batches:

1. Create a function that returns the oldest N objects needing processing (for example, oldestNObjectsWithBlankField(int count) that returns objects ordered by last edited timestamp with a limit).
2. Configure your automation to use a function-generated object set that calls this function.
3. Manually execute the automation repeatedly with a reasonable batch size, waiting for each execution to complete.
4. Continue manual executions until the backlog is reduced below the limit (typically <100K objects).
5. Once the backlog is manageable, your regular condition-based automation can process new objects as they arrive.

Execution settings

Execution settings expose a number of configurable parameters:

• Specify object set: For object set conditions, you can specify an input object set. See documentation on limits for object set size restrictions. This object set must contain objects of the same type as configured in the automation condition. All objects in this set will trigger the automation and be passed into any effect using New object parameters. Three object set types are currently supported:

  • Defined object set: Static (manually selected objects), or dynamic (defined by filters on a chosen object set).
  • Saved object set: An object set saved as a Palantir resource.
  • Function-generated object set: Choose a function and define its parameters with static values. This function must return an object set of the same object type as the condition object set.

• Batch size: Batch size determines the number of objects in each execution. For example, if the batch size is 100 objects, and there are 1,000 objects in the defined object set, then the automation will have 10 individual executions (each with 100 objects), scheduled 1 minute apart. Objects are partitioned in a nondeterministic, random ordering.

  • Batch size is not visible to configure if the automation's condition does not involve an object set.

• Parallelism: Parallelism specifies how many batches should run in parallel. A higher number leads to faster execution.

• Recipients: Manual execution supports sending notifications to all users.
  
  

  When a manual execution is triggered, the object set is evaluated using the token of the user who initiated the execution. This ensures that the evaluation respects permissions and access rights of the executing user.