Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] I Set activity Finish after for loop break but it still call httprequest again #5630

Open
Thuylinh28 opened this issue Jun 19, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@Thuylinh28
Copy link

Description

I Set activity Finish after for loop break but it still call httprequest again

Steps to Reproduce

image
image

@Thuylinh28 Thuylinh28 added the bug Something isn't working label Jun 19, 2024
Copy link

glime-ai bot commented Jun 19, 2024

To assist you with the issue where an activity is being called again after a loop break, I would need to see the actual workflow definition JSON or the code that defines the workflow. The images provided in the steps to reproduce do not give enough context to understand the exact problem or to provide a solution.

However, based on the information provided, it seems like there might be an issue with the way the loop and the subsequent activities are configured. If the Finish activity is being triggered after a Break activity within a loop, but the HttpRequest activity is still being called, it could indicate that the Break activity is not properly terminating the loop, or there might be another path in the workflow that leads to the HttpRequest activity being executed.

To troubleshoot this issue, please check the following:

  1. Ensure that the Break activity is correctly placed within the loop and that the condition for breaking out of the loop is being met.
  2. Verify that there are no additional transitions from other activities that could lead to the HttpRequest activity being called after the loop is supposed to be terminated.
  3. Review the workflow definition JSON to ensure that the activities and transitions are correctly defined.

If you can provide the workflow definition JSON or the code that defines the workflow, I can give you a more precise answer. Otherwise, you may need to debug the workflow execution to see why the HttpRequest activity is being called again.

This comment was generated by Glime.

@Thuylinh28
Copy link
Author

this is my workflow
noti-expire-sla.json
and this is input :
{
"ListNoti": {
"TenantId": null,
"Id": "00000000-0000-0000-0000-000000000000",
"Case_Id": "91c67bd6-cad8-35c0-cf4a-3a133c61bf76",
"ParentId": "de93ffc3-741d-eb82-d524-3a128c8b78f6",
"ParentName": "SLA",
"Status": null,
"BoPhanName": null,
"Description": "sonlv có Ticket 24061800012 quá hạn SLA",
"NumberNotification": null,
"ConcurrencyStamp": null,
"NotificationId": null,
"Type": null,
"TypePersonReceiveNoti": null,
"CurrentLanguage": "vi",
"HandleUsername": "sonlv",
"IncidentCode": "24061800012"
},
"ParentName": "SLA",
"Type": "App",
"NumberNoti": "2",
"UrlAPP": "https://localhost:44380",
"TimeNoti": "10"
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant