Logic App triggers immediately upon Enable, despite specifying the 'Start Time'
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- azure
- Domain
- cloud
Research direction
Start by reproducing the documented deployment, recurrence-trigger edit, future Start Time, and Enable sequence described in the issue. Compare it with the export-template redeployment workaround and verify that the Logic App remains idle until the specified start time; consult the linked Azure Logic Apps scheduling documentation while investigating.
Written by the indexing model from the issue text.
Description
After deploying the start/stop solution, the Logic Apps begin in 'Disabled' state. After editing the recurrence trigger to include a 'Start Time' parameter in the future and then 'Enable' the Logic App, it is triggered automatically and does not honor the specified start time.
But, according to docs, When using a start time in the future, it runs the first workload no sooner than the start time, based on the schedule calculated from the start time. So, the workflow should not fire until the specified start time.
I did notice a workaround that seems to help fix it but am unable to explain the behavior -
We were able to overcome the unexpected behavior by editing the Logic App and then creating a new identical version of it. The process is as follows:
Deploy Start/Stop solution
Edit the Logic App recurrence trigger, save changes
Under the Logic App Automation tab >> Export template >> Deploy
Enable new redeployed Logic App
- Dominant language
- No language data
- Stars
- 58
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/startstopv2-deployments
-
.NET version support Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/startstopv2-deployments#155 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
microsoft/startstopv2-deployments#149 · 2 comments ·
All issues in microsoft/startstopv2-deployments
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
Feature needs-triage pulumi/registry
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
infrastructure launch: scale production
Difficulty 2/5 Half a day Newbie friendliness 72/100
Practitionist/familiarise_web#1772 ·