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

Logic App workflow is triggering 2 hours late and twice #1261

Closed
onyx-lemur opened this issue Dec 5, 2024 · 4 comments
Closed

Logic App workflow is triggering 2 hours late and twice #1261

onyx-lemur opened this issue Dec 5, 2024 · 4 comments
Labels

Comments

@onyx-lemur
Copy link

onyx-lemur commented Dec 5, 2024

Describe the Bug with repro steps

  1. Workflow is set up to run at 19:45 every day, which has been happening successfully for a number of months now. Business critical processes trigger around 20:00, which are dependent on a successful run.
  2. We have reports of workflows running at 21:42, 2 hours beyond the trigger date
  3. They have also been run twice.

What type of Logic App Is this happening in?

Standard (Portal)

Which operating system are you using?

Windows

Are you using new designer or old designer

New Designer

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

Workflow JSON

Screenshots or Videos

Image

Image

Browser

Chrome

Additional context

I suspect there was some kind of Azure failure and these have been queued up. However, is there documentation around this behaviour that I can allay customer fears with?

@rllyy97
Copy link

rllyy97 commented Dec 5, 2024

Hi @onyx-lemur, can you open a support case for this? It does not appear to be a UX issue, and opening a support case is the best way to get backend issues resolved.
I am going to leave this open, but I will be transferring it over to our backend repo.

@rllyy97 rllyy97 transferred this issue from Azure/LogicAppsUX Dec 5, 2024
@onyx-lemur
Copy link
Author

@rllyy97 Will do - thanks for responding!

Copy link

This issue is stale because it has been open for 45 days with no activity.

@github-actions github-actions bot added the stale label Jan 25, 2025
Copy link

github-actions bot commented Feb 8, 2025

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions github-actions bot closed this as completed Feb 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants