Issues with triggers in debug

Help Activities
, , ,
1

My team is attempring to use a Dynamics CRM Trigger to check for updates and kick off a process. When we use the test trigger button on the trigger we get results, but if we attempt to use the debugger we get the following error. This occurs both in the online Studio and StudioX.

2024-10-01 13:45:25.718 GMT−4:	Error: UiPath.IntegrationService.Activities.Runtime.Exceptions.RuntimeException: Trigger activity could not find any matches. Error code: DAP-RT-1052.
   at UiPath.IntegrationService.Activities.Runtime.Activities.ConnectorTriggerActivity.DebugExecuteAsync(IExecutionService executionService, ExecutionParameters executionParameters, CancellationToken token)
   at UiPath.IntegrationService.Activities.Runtime.Activities.ConnectorTriggerActivity.ExecuteAsync(AsyncCodeActivityContext context, CancellationToken token)
   at UiPath.IntegrationService.Activities.Runtime.Activities.AsyncTaskCodeActivityImplementation.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)
   at UiPath.IntegrationService.Activities.Runtime.Activities.AsyncTaskCodeActivity.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)
   at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)

If we deploy the process then it will properly trigger. Do triggers just not function in debug? Or is there something we can do to get the information in the trigger from into debug?

2

Hi!

You’re using a trigger in integration service?

Integration Service - Triggers (uipath.com)

image
image1640×104 20.8 KB

I might be wrong, but I think you need to use DEV or Testing for it to work in debug?

4

@trotter

Try this:

The error encountered in UiPath when using a Dynamics CRM Trigger during debugging is common and stems from how triggers interact with the debugging environment.

Understanding Triggers:

  • Functionality: Triggers respond to events, such as updates in Dynamics CRM, but may not execute as expected in debug mode, leading to errors such as “Trigger activity could not find any matches.”
  • Testing: The “Test Trigger” button simulates events, allowing you to see results without engaging the full debugging process.

Debugging Limitations:

  • Step-by-step debugging of triggers is generally unsupported since they depend on external events.
  • You cannot debug the execution flow directly in debug mode.

Alternative Debugging Approaches:

  1. Logging: Implement detailed logs to track workflow activities.
  2. Breakpoints: Place breakpoints in the workflow initiated by the trigger to inspect variable states.
  3. Local Testing: Modify Dynamics CRM to simulate trigger events for practical testing.
  4. Simulation: Create a mock environment to replicate Dynamics CRM updates for workflow testing.
1 Like
5

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.