Status Update
Comments
ro...@stone.com.br <ro...@stone.com.br> #2
There is not enough information here to be actionable. Please open a new issue with additional information.
ah...@ezoic.com <ah...@ezoic.com> #3
Additional Context:
Issue seems to have started at around 1am PST today.
Issue seems to have started at around 1am PST today.
bl...@google.com <bl...@google.com> #4
Automated by Blunderbuss job workspace-devrel-public-issue-tracker-blunderbuss-autoassigner for component 191640.
pi...@gmail.com <pi...@gmail.com> #5
Comment has been deleted.
jo...@sanmina.com <jo...@sanmina.com> #6
Time triggers don't work for me too. Noticed today around 10 CST
ro...@stone.com.br <ro...@stone.com.br> #7
Any updates?
de...@madwire.com <de...@madwire.com> #8
Same issue here.
jp...@google.com <jp...@google.com> #10
Please see https://issuetracker.google.com/326802543 .
> We received an earlier report of issues with triggers/API related errors however, engineering confirmed there was a queued backlog which caused delays. We expect the backlog should be cleared in a few hours.
> We received an earlier report of issues with triggers/API related errors however, engineering confirmed there was a queued backlog which caused delays. We expect the backlog should be cleared in a few hours.
Description
Before opening a new issue, please search for other related issues , click the ★ to subscribe to updates, and click
+1
to vote.Description
Time based triggers do not run for some users in the workspace, or they trigger intermittently with significant delays.
Code
Output
Finished setting up new triggers.
Steps