Closed ShingoHanai closed 8 months ago
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
Describe the Bug with repro steps
Following preview content, gives a false impression this trigger runs at 12:00.
Actually trigger runs at 12:mm because “At these minutes” parameter isn’t exactly set and “mm” is set from last trigger run datetime.
I think it is better to fix expression like this.
Set each parameters like this
Interval : 1
Frequency : day
At these hours 12 (For example)
What type of Logic App Is this happening in?
Consumption (Portal)
Are you using new designer or old designer
Old Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos
No response
Browser
Chrome and MS Edge
Additional context
No response
AB#25422917