-
Notifications
You must be signed in to change notification settings - Fork 4
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
Substring" with "2" argument(s): "Length cannot be less than zero. (Parameter 'length') #26
Comments
I'm getting the same error as @acieslik This is my logic app (security related data was replaced with fake names or numbers):
|
Hi @acieslik, Sorry for not responding earlier. I was a bit busy and on holiday. Hope to find some time next weeks. /Stefan |
Hi @acieslik , after my initial investigation it might be caused by the the async_response action which is nowhere configured as a runafter property of one of the other actions. To determine the order of the actions I try to use the runafter property. Any thoughts on how to determine the order of the actions when an async_response is being used? |
Hi @acieslik, This is the result I've now when doing some refactoring. Can you confirm this is a correct representation of the flow? https://gist.github.com/stefanstranger/9681324a42b297a6749cd1505e62af94 |
HI @hsncrook, I've made some changes to the code and I've now the following result: https://gist.github.com/stefanstranger/bd69c9e7d8a3486205f4567949ef52a2 Can you please validate if this is correct now? Regards, |
When using this logic app definition the Helper function GetAction will fail, as for some reason an array of actions return instead of one currentAction as the name implies:$_.RunAfter -eq $ (('{0}-False') -f $(($cur …
Where-Object: C:\Repos\github\logicappdocs_ac\src\Helper.ps1:173:76
Line |
173 | … ($Actions | Where-Object {
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Exception calling "Substring" with "2" argument(s): "Length cannot be less than zero. (Parameter 'length')"
(security related data was replaced with fake names or numbers):
The text was updated successfully, but these errors were encountered: