Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
That was a strange behavior but it started working again so we decided to watch it to see if it happened again. Then on November 25th (Saturday) it happened again.
We don't know why this happens but the pattern is that all 3 times happened over the weekend.
We know tasks were created because we can see it in the Cloud Tasks logs that tasks were created but the execution logs are missing for those 3 days.
Usually when it works we can see 2 logs per task (1 for task created and 1 for execution). These 3 days had the creation log but not the execution log.
Problem you have encountered: Tasks are created in Cloud Tasks via the SDK but Cloud tasks doesn't trigger the tasks
What you expected to happen: Cloud tasks to actually trigger the tasks
Steps to reproduce: Create the tasks via the SDK. It's a bit unpredictable because it only happened 3 times in the last month. But all 3 happened over the weekend.