Error while executing second Transaction in RE framework

Help Action Center
,
1

I am getting the following Error “Unable to Start Execution” in Wait for Validation Activity for Second transaction in RE framework.

System.Text.RegularExpresson.Match cannot be serialised .Consider marking with Data Cotracts Attribute

2

@Haneesh_P

Are you using any regular expressions in your code
if you are using instead of System.Text.RegularExpresson.Match this System.Text.RegularExpresson.Regex.Match use this

3

@Haneesh_P

Welcome to the community

as per rule only serializable variables can be used in same scope as the persistent activities…try to remove the variables from the scope

please check best practices

The image contains a bullet point describing that variables not used in long-running scopes are exempt from serialization, provided they are within specific wait and resume activities, with examples of such activities like "Wait for Job and Resume" and "Wait for Queue Item and Resume" linked in blue text. (Captioned by AI)
The image contains a bullet point describing that variables not used in long-running scopes are exempt from serialization, provided they are within specific wait and resume activities, with examples of such activities like "Wait for Job and Resume" and "Wait for Queue Item and Resume" linked in blue text. (Captioned by AI)1041×115 24 KB

cheers

4

Actually first transaction (pdf file ) is exceutng succesfully with same code .for second transaction only this issue.
If the second transaction is run stand alone .It executes without any issue.

5

Can you debug the code and find at which action it throwing error

6

It seems that the issue might be related to how the transactions are being processed in sequence. If the first transaction executes successfully but the second one fails when run consecutively, it could suggest that the code does not correctly clear the current transaction in memory and get the next one.

See if any variables are storing details and not getting replaced with the next transaction details. Kindly debug and put a break point for the second transaction details. Analyze the variable values and see if there is any possibility for the above suggestion