web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / [BUG] Timer Start with...
Power Apps
Unanswered

[BUG] Timer Start with variable not working

(0) ShareShare
ReportReport
Posted on by 322

Hello,

can you please check if this is happening to you too:

- timer with autostart to true (but I also tried without it)

- Start is a variable which is triggered by the UpdateContext({startVariable:true});UpdateContext({startVariable:false});

-TimerOnStart /OnEnd: ClearCollect(colExample, [filtering SQL code here])

- timer time set to 1

 

When I first navigate on the screen, everything works and the data is being collected. but, clicking a button that fires off the Start variable, causes no action on the timer. I used a label to see if the variable changes true/false, and it does.

 

Clicking on the timer also does nothing. I also tried putting a variable on the Reset property and using both variables, but no effect.

 

Version: PowerApps 3.21023.26, Edge Chromium

 

If this is no longer a supported feature, please provide alternatives. The objective is to have a code that runs on screen visible, but that can be "called" as needed, without having to copy-paste and maintain the same code on different locations.

Categories:
I have the same question (0)
  • WarrenBelz Profile Picture
    153,034 Most Valuable Professional on at

    Hi @vladimir84 ,

    Have you tried a Global Set() Variable?

     

    Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

  • vladimir84 Profile Picture
    322 on at

    I haven't actually. But why would it matter?

  • WarrenBelz Profile Picture
    153,034 Most Valuable Professional on at

    @vladimir84 ,

    Try it - I have found the same issue a while ago and a global variable set/reset fixed it.

    I just also noticed also that you have the set the wrong way around - if you want to start a timer on true, you need to set false then true.

     

    Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

     

     

  • WarrenBelz Profile Picture
    153,034 Most Valuable Professional on at

    Hi @vladimir84 ,

    Just checking if you got the result you were looking for on this thread. Happy to help further if not.

    Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

  • vladimir84 Profile Picture
    322 on at

    Hi @WarrenBelz ,

    thanks for checking in. It's a very frustrating situation, as UpdateContext is working in another app on another environment. It's really difficult to develop when after hours of work you discover that an integral part of the platform is not working the way it was supposed to.

     

    Now, I don't know if I should convert all updatecontexts to Set, like you suggested, or abandon the whole idea and stick with On Visible and repeat the code in buttons.

     

    Whichever the choice, it's going to be hours of work, because the apps are complex.

     

  • vladimir84 Profile Picture
    322 on at

    I have a new situation where (on the same screen) the timer gets triggered properly and on another button,

    the timer is triggered, "something happens" as I see the dots circulating and the SQL is properly patched (1st paragraph of the code), but the collection is not refreshed (second paragraph of the code that triggers the timer). When I leave the screen and come back, the timer is auto started and the collection is properly refreshed.

     

    It's just too unreliable. 

     

  • steve_hendy Profile Picture
    385 on at

    In the on visible of a screen I have UpdateContext({TimerReset: true});UpdateContext({TimerReset: false});Reset(Timer1_2);UpdateContext({TimerStart:false});UpdateContext({TimerStart:true})

     

    TimerReset variable is in the Reset field of the timer and TimerStart is in the Start field of the timer. 

     

    I only built this today and it works perfectly every time.

  • Verified answer
    kevinlowe Profile Picture
    66 on at

    So I found this thread today when I thought I had the same issue.  In my case, I was just being stupid and not playing my app (was just alt-clicking my button, which does nothing to a timer).  Doh!

     

  • test222221 Profile Picture
    46 on at

    @kevinlowe thanks 😅, i've been trying to use timer for like 2 months now but i didn't even try to play my app, now everything is clear why my timer didn't work😅

  • MattiasP1 Profile Picture
    138 on at

    You saved me alot of time. Thanks !

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 717 Most Valuable Professional

#2
Michael E. Gernaey Profile Picture

Michael E. Gernaey 329 Super User 2025 Season 2

#3
Power Platform 1919 Profile Picture

Power Platform 1919 268

Last 30 days Overall leaderboard