# General Translation Platform: Viewing automation activity
URL: https://generaltranslation.com/en-US/docs/platform/locadex/guides/viewing-automation-activity.mdx
---

title: Viewing automation activity
description: How to inspect Locadex automation runs, their status, errors, branches, and pull requests.
related:
  links:
    - /docs/platform/locadex/guides/configuring-automations
    - /docs/platform/locadex/guides/auto-merging-prs
    - /docs/platform/locadex/guides/managing-languages
    - /docs/platform/locadex/guides/using-in-monorepos

---

Use automation activity to see what Locadex ran, when it ran, and whether it completed.

## View Project activity [#project-activity]

Open **Project > Automations**.

The **Recent activity** section shows the five latest runs across the Project. Select an automation to see up to 20 recent runs for that automation.

Expand a run to review its trigger, step progress, duration, branch, pull request number, and customer-safe error details.

## Diagnose a failed run [#failed-runs]

1. Expand the failed run and find the first failed step.
2. Read the customer-safe message and copy the error code shown in the run failure header.
3. Check the branch or pull request when one exists to see which files changed before the failure.
4. Correct the Project configuration, dependency, command, or repository access named by the message.
5. Start the automation manually, or retrigger it through its configured event.

The error code identifies the stage that failed:

- `CONFIG_ERROR`, `VALIDATION_FAILED`, and `DRY_RUN_FAILED` indicate invalid automation, Project configuration, or generated changes that did not pass validation.
- `CUSTOM_COMMAND_FAILED` indicates a pre-process or post-process command returned a failure. Run the same command in the repository and correct its dependencies or script.
- `GIT_CLONE_FAILED`, `GIT_COMMIT_FAILED`, and `GIT_PUSH_FAILED` indicate repository access or Git operation failures. Check the GitHub connection and branch protections.
- `TRANSLATION_FAILED` indicates translation processing did not complete. Check the run message and source content, then retry.
- `SANDBOX_ERROR`, `IO_ERROR`, and `DATA_ERROR` indicate environment, file, or generated-data failures.
- `WORKFLOW_TIMEOUT`, `WORKFLOW_CANCELLED`, and `WORKFLOW_ABORTED` indicate that the run did not reach completion.
- `LOCADEX_RUN_ERROR` and `INTERNAL_ERROR` are general failures. Retry once, then include the run ID and error code when contacting support.

Locadex keeps raw stack traces and internal details out of customer-facing activity. The message and error code are the safe values to include in a support request.

Failed runs show a terminal status for every step rather than leaving steps active, and a run that stops unexpectedly is marked failed and releases its branch so a later run can use it.

## View Organization activity [#organization-activity]

Open **Organization > Locadex > Automations** to search automations across Projects. Select an automation to inspect its recent runs and targets.

Organization-level access is useful when the same team manages several Projects. Project names appear on each run.

## See pull requests [#see-pull-requests]

If a run created or updated a pull request, use its pull request number to find the change in GitHub.

Use the pull request to review files, checks, comments, and merge status.

## Retry failed work [#retry-failures]

Expand a failed run and use its customer-safe error details to resolve the cause. For an automation run, return to the automation detail page and click **Run now**. For a setup run, wait for **Run setup** to become available again, then retry setup.

## Next steps

- /docs/platform/locadex/guides/configuring-automations
- /docs/platform/locadex/guides/auto-merging-prs
- /docs/platform/locadex/guides/managing-languages
- /docs/platform/locadex/guides/using-in-monorepos