---
title: "Troubleshoot trigger issues"
slug: "troubleshoot-trigger-issues"
tags: ["Task topic"]
status: "update"
updated: 2026-09-22T13:18:59Z
published: 2026-09-22T13:18:59Z
canonical: "docs.staedean.com/troubleshoot-trigger-issues"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot trigger issues

An integration can be triggered in several ways. If a trigger fails, no errors are shown in the **Connectivity studio - Integration operations** workspace on the **History** tab.

## Batch job

You can run a project, message or web service in batch, usually in recurring mode. If the message or web service does not run at all, the [batch server](https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/sysadmin/batch-processing-overview) can be down.

## Custom code

You can [run a message from custom code](/data-management/docs/run-a-message-from-custom-code). If you use custom code to run a message, and the message does not run, probably, the custom code is not right. You need a developer to check and repair the custom code.

## SQL triggers

You can run an integration using data synchronization setup with table events, using SQL triggers. If events are not logged in the data synchronization log, the SQL triggers can be missing. To solve this issue, you can [review and recreate the SQL triggers](/data-management/docs/monitor-and-recreate-sql-triggers).

## Related

- [Run a message from custom code](/run-a-message-from-custom-code.md)
- [Monitor and recreate SQL triggers](/monitor-and-recreate-sql-triggers.md)