# scheduled Published articles for scheduled. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The Autonomous Dumbledore DevFeed: [The Autonomous Dumbledore]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-04-25T22:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [API](), [Job](), [test](), [maintenance](), [Code]() Tags: [api](), [bugs](), [engineering](), [feature](), [fetch](), [job](), [maintenance](), [news](), [running](), [scheduled](), [test](), [tests](), [web-frontend]() ### AI overview An intern at Khan Academy describes the Autonomous Dumbledore, a system that monitors PSAT score-linking endpoints through recurring tests and automatically enables or disables the related feature based on recent results. ### Source excerpt By Evy Kassirer When I arrived at Khan Academy to start my internship on the Official SAT Practice ... Read more ## Announcing instance preference lists for Amazon SageMaker AI training jobs DevFeed: [Announcing instance preference lists for Amazon SageMaker AI training jobs]() Original publisher: [Read original article]() Author: Kanwaljit Khurmi Published: 2026-09-15T16:01:47Z Content type: release Language: en Sources: [Artificial Intelligence]() Topics: [Amazon SageMaker AI](), [GPU](), [Model Development](), [data-processing]() Tags: [amazon-sagemaker-ai](), [announcements](), [gpu](), [intermediate-200](), [model-development](), [pipelines](), [scheduled](), [training]() ### AI overview Amazon SageMaker AI introduces instance preference lists for training and processing jobs. Users can specify up to five instance types in priority order, and SageMaker AI launches the job on the first option with available capacity, reducing manual retries and capacity monitoring. ### Source excerpt Amazon SageMaker AI now offers instance preference lists for training and processing jobs. Specify an ordered list of up to five instance types, and SageMaker AI automatically launches on the first type with available capacity, eliminating manual retry loops and capacity-watching scripts. ## Announcing DocumentsDB: Documents that evolve with your product DevFeed: [Announcing DocumentsDB: Documents that evolve with your product]() Original publisher: [Read original article]() Author: Arnab Chatterjee Published: 2026-09-02T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Databases](), [GeoJSON](), [SDKs]() Tags: [announcements](), [database](), [json](), [product](), [products](), [scheduled](), [sdk](), [snapshots](), [transactions]() ### AI overview Appwrite announces DocumentsDB, a schemaless database for flexible JSON documents whose fields can evolve without defining columns or running schema migrations. It supports Appwrite SDK patterns and database capabilities such as permissions, queries, transactions, bulk operations, imports, exports, and backups. ### Source excerpt Store flexible JSON documents, query them with the Appwrite SDKs, and let your data model evolve with your product instead of ahead of it. ## Give a scheduled agent access to a user's Google, Slack, and Jira with no signed-in session DevFeed: [Give a scheduled agent access to a user's Google, Slack, and Jira with no signed-in session]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-12T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [Tutorial](), [API keys](), [Authorization](), [OAuth](), [Slack](), [Google]() Tags: [agent](), [api](), [audit](), [auth0](), [authorization](), [autonomous-agents](), [browser](), [google](), [jira](), [logging](), [rotation](), [scheduled](), [scopes](), [slack](), [token](), [tokens](), [tutorial]() ### AI overview A tutorial showing how to give scheduled workers access to a user's Google, Slack, and Jira through WorkOS Pipes without a signed-in session. It covers scoped credential retrieval, token relay, rotation, revocation, and audit logging. ### Source excerpt A runnable tutorial for pulling per-connection third-party credentials from WorkOS Pipes with nobody logged in, plus relay, rotation, revocation, and audit logging. ## Batch Jobs for SparkClient: Submitting and Managing Spark Workloads from Python DevFeed: [Batch Jobs for SparkClient: Submitting and Managing Spark Workloads from Python]() Original publisher: [Read original article]() Author: Sameer Yadav Published: 2026-07-25T05:00:00Z Content type: tutorial Language: en Sources: [Kubeflow]() Topics: [Apache Spark](), [SDKs](), [Python](), [Kubernetes]() Tags: [batch](), [cleanup](), [gsoc](), [jobs](), [kubernetes](), [logs](), [pipelines](), [python](), [scheduled](), [sdk](), [spark]() ### AI overview This tutorial explains how the Kubeflow SDK's SparkClient supports submitting and managing batch Spark workloads on Kubernetes from Python. It covers script- and function-based jobs, lifecycle operations, log retrieval, cleanup, and the implementation's current boundaries. ### Source excerpt How the SparkClient SDK's new batch job APIs work under the hood -- submit_job(), FileJob/FuncJob, the lifecycle APIs, and log retrieval. ## Upcoming Changes to the Nearby Connections API DevFeed: [Upcoming Changes to the Nearby Connections API]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-07-20T13:00:00Z Content type: release Language: en Sources: [Android Developers Blog]() Topics: [API](), [Bluetooth](), [Wi-Fi](), [Android]() Tags: [2026](), [android](), [api](), [bluetooth](), [developers](), [privacy](), [scheduled](), [wi-fi](), [workflows]() ### AI overview Android is changing the Nearby Connections API so it will no longer automatically enable Wi-Fi or Bluetooth radios for first- and third-party applications. Developers must ensure the radios are enabled and notify users when manual activation is required. The change is scheduled for late 2026. ### Source excerpt Posted by Wei Wang, Engineering Manager, Android BeTo User privacy and transparency are core to the Android experience. To better align with these principles, we are updating the default behavior of the Nearby Connections API regarding how it interacts with device radios. What is changing? Previously, the Nearby Connections API could automatically toggle Wi-Fi and Bluetooth radios ON to facilitate connections without explicit user intervention. Moving forward, the API will no longer automatically enable these radios for 1P and 3P applications. What this means for developers If your app relies on Nearby Connections, you will need to update your implementation to account for these changes: Manual Radio Management: You must ensure that the necessary radios (Wi-Fi or Bluetooth) are enabled before initiating Nearby Connections tasks. User Notification: If the required radios are disabled, your app must now inform the user and request that they enable them manually. The API will no longer programmatically turn them on for you. Timing These changes are scheduled to take effect in late 2026. We recommend reviewing your connection workflows now to ensure a seamless transition for your users. ## Examples of Agent Goals, Loops, and Scheduled Workflows in Codex and Claude Code DevFeed: [Examples of Agent Goals, Loops, and Scheduled Workflows in Codex and Claude Code]() Original publisher: [Read original article]() Author: Owain Lewis Published: 2026-07-02T07:01:00Z Content type: article Language: en Sources: [The AI Engineer]() Topics: [codex](), [Loop Engineering](), [Automation](), [Claude Code](), [Pull Request](), [GitHub Issues](), [ci]() Tags: [agent](), [ai-agents](), [automation](), [ci](), [claude-code](), [codex](), [github-issues](), [logs](), [review](), [scheduled](), [tests](), [workflow]() ### AI overview The article explains how prompts, goals, recurring runs, and workflows differ, then presents examples of using agents for recurring engineering tasks. It emphasizes evidence, stop rules, tests, CI, logs, issues, pull requests, and human review as safeguards because agents can misunderstand context or make mistakes. ### Source excerpt Practical ways to combine prompts, goals, and scheduled runs in Codex and Claude Code. ## What Is ACH Payment? A Complete Guide for SaaS Founders DevFeed: [What Is ACH Payment? A Complete Guide for SaaS Founders]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-05-27T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [Transactions]() Tags: [ach](), [bank](), [batch](), [business](), [compliance](), [cost](), [guide](), [payment](), [payments](), [saas](), [scheduled](), [standard](), [us]() ### AI overview This guide explains ACH payments for SaaS companies, including how the US bank-transfer network works, why ACH fees can be lower than card fees, settlement timelines, and options for accepting ACH without operating a merchant account. ### Source excerpt ACH payments explained for SaaS - how they work, why they cost 10x less than cards, settlement timelines, and how to accept them without your own merchant account. ## Announcement: Xcode15 Deprecation in Semaphore DevFeed: [Announcement: Xcode15 Deprecation in Semaphore]() Original publisher: [Read original article]() Author: Pete Miloravac Published: 2026-05-12T10:56:42Z Content type: release Language: en Sources: [Semaphore Engineering]() Topics: [Xcode](), [ci](), [macOS]() Tags: [announcement](), [ci](), [deprecated](), [lifecycle](), [product-news](), [scheduled](), [september-2026](), [switching](), [xcode]() ### AI overview Semaphore announces the deprecation and end of life of its macOS Xcode15 build environments. Brownout periods will precede removal on July 6, 2026, and users are advised to migrate their pipelines to a supported Xcode version, preferably Xcode26. ### Source excerpt MacOS Xcode15 reached the end of its supported lifecycle on Semaphore. To ensure the security, reliability, and maintainability of our platform, we are announcing the deprecation and end of life of MacOS Xcode15 build environments. Semaphore users should consider switching to Xcode26 as Xcode16 is scheduled for deprecation in September 2026. Why We're Deprecating Xcode15 [...] The post Announcement: Xcode15 Deprecation in Semaphore appeared first on Semaphore. ## The Quiet Shift: How AI Is Reshaping Product Work DevFeed: [The Quiet Shift: How AI Is Reshaping Product Work]() Original publisher: [Read original article]() Author: Nela De Silva Published: 2026-05-03T09:11:35Z Content type: opinion Language: en Sources: [Kogan.com]() Topics: [Artificial Intelligence](), [Automation]() Tags: [ai](), [automation](), [productivity](), [research](), [scheduled]() ### AI overview The article examines how AI is becoming part of day-to-day product work. It describes applications including scheduled automation, customer session analysis, meeting capture, team skill building, and codebase exploration, arguing that AI can reduce recurring coordination work and support higher-judgment activities without replacing prioritisation, scoping, or stakeholder alignment. ### Source excerpt Over the last several months, AI has moved from a side experiment to an integral part of day-to-day product practice. The shift is practical rather than theoretical, but it is still very much in motion. Recurring coordination work is beginning to take meaningfully less time, while the substantive work that defines the role, such as problem framing, solution shaping, navigating trade-offs, and stakeholder alignment, is becoming sharper and better supported. This piece sets out where the shift is taking hold and the practical improvements that are pointing towards meaningful productivity gains within the product team, and, as a result, beyond it. Where product teams can apply AI From my own experience in the role, the most significant value has emerged across five principal areas: scheduled background automations, customer session analysis, meeting capture and follow-up, skill building for the wider team, and codebase exploration. These five areas serve two complementary purposes. In some, such as scheduled automations, ticket triage, and meeting capture, recurring and semi-structured work can be shifted toward AI-assisted execution, freeing capacity for higher-judgement activities. In others, such as codebase exploration and customer session analysis, AI actively extends what someone in a product role can contribute, opening up investigation and insight that would previously have depended on engineering or research support. In both cases, AI complements rather than replaces the substantive work of prioritisation, scoping, and stakeholder alignment. Let's take a closer look at how this translates into practice. Figure 1. The five areas of AI application, organised against two complementary purposes. A lightweight test for what to automate The strongest candidates for automation are rarely the most complex tasks; the opposite is usually true. The greatest returns come from work that is repetitive, predictable, and quietly consuming time in the background. A simple thre ## Ask Your Survey Anything: Building AI Analysis Pipelines with Airflow 3 DevFeed: [Ask Your Survey Anything: Building AI Analysis Pipelines with Airflow 3]() Original publisher: [Read original article]() Author: Apache Airflow Published: 2026-04-15T00:00:00Z Content type: tutorial Language: en Sources: [Apache Airflow Blog]() Topics: [airflow](), [Artificial Intelligence](), [Large Language Model](), [SQL](), [CSV](), [data]() Tags: [ai](), [airflow](), [apache-airflow](), [automated](), [community](), [configuration](), [csv](), [executor](), [llm](), [pipelines](), [providers](), [scheduled](), [sql](), [tutorial]() ### AI overview A tutorial showing how to build interactive and scheduled AI analysis pipelines with Airflow 3. The pipelines use survey CSV data, generate and run SQL queries, validate schemas, and either request human approval or email results automatically. ### Source excerpt The 2025 Airflow Community Survey collected responses from nearly 6,000 practitioners across 168 questions. You can open a spreadsheet and filter, or write SQL by hand. But what if you could just ask a question and have Airflow figure out the query, run it, and bring the result back for your approval? This post builds two pipelines that do exactly that, using the apache-airflow-providers-common-ai provider for Airflow 3. The first pipeline is interactive: a human reviews the question before it reaches the LLM and approves the result before the DAG finishes. The second is scheduled: it downloads fresh survey data, validates the schema, runs the query unattended, and emails the result. If you haven't seen the common.ai provider overview yet, start there for a tour of all the operators. This post goes deep on a concrete end-to-end example. Two Pipelines, One Example File Both DAGs live in example_llm_survey_analysis.py and share the same schema context and datasource configuration. example_llm_survey_interactive: trigger manually, review at both ends: prompt_confirmation -> generate_sql -> run_query -> extract_data -> result_confirmation (HITLEntryOperator) (LLMSQLQuery) (Analytics) (@task) (ApprovalOperator) example_llm_survey_scheduled: runs @monthly, no human in the loop: download_survey -> prepare_csv -> check_schema -> generate_sql -> run_query -> extract_data -> send_result (HttpOperator) (@task) (LLMSchema (LLMSQLQuery) (Analytics) (@task) (@task / Email) Compare) The Data The Airflow Community Survey 2025 CSV has 5,856 rows and 168 columns covering everything from Airflow version and executor type to cloud provider, company size, and AI tool usage. A few highlights from the data: 3,320 respondents identify as Data Engineers 2,032 use AWS as their primary cloud provider for Airflow 1,445 are already running Airflow 3 1,351 say they often use AI tools to write Airflow code Those last two numbers together are part of why this example exists: the people most likely to use th ## Checkpoint #9: Apr 2026 DevFeed: [Checkpoint #9: Apr 2026]() Original publisher: [Read original article]() Author: EF Protocol Support Published: 2026-04-10T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Development](), [Protocol (disambiguation)]() Tags: [2026](), [compatibility](), [complexity](), [consensus](), [ethereum](), [feature](), [implementation](), [protocol](), [research-development](), [scheduled](), [state](), [update](), [upgrade]() ### AI overview This checkpoint summarizes Ethereum core development. Glamsterdam implementation is progressing, but ePBS, gas repricing, and Block-level Access Lists remain technically complex. Hegotá has selected FOCIL as a major feature and plans work on Account Abstraction as a minor feature, while developers prepare additional devnets. ### Source excerpt Ethereum's All Core Developer calls can be a lot to keep up with, so this "Checkpoint" series aims for periodic high-level updates, depending on what's happening in core development. See the previous update here. !image... ## Keeping sponsor lists up-to-date DevFeed: [Keeping sponsor lists up-to-date]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2026-03-25T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Tool](), [GitHub](), [GitHub Actions](), [Go Language](), [configuration](), [Template](), [sensitive data]() Tags: [commit](), [configuration](), [github](), [github-actions](), [go](), [scheduled](), [sensitive-data](), [template]() ### AI overview The article introduces a Go tool that automates updating sponsor lists across README files and websites. It fetches sponsors from GitHub Sponsors and OpenCollective, renders content with Go templates, supports shared configuration and remote templates, and can run daily through GitHub Actions with automatic commits. ### Source excerpt Keeping sponsor lists up-to-date across multiple READMEs and websites is tedious - so I wrote a tool to automate it. ## No Permanent Overrides DevFeed: [No Permanent Overrides]() Original publisher: [Read original article]() Author: Matt McKenna Published: 2026-03-24T13:00:00Z Content type: tutorial Language: en Sources: [Matt McKenna]() Topics: [Development](), [incident](), [maintenance](), [audit]() Tags: [audit](), [automatic](), [best-practices](), [feature](), [feature-flags](), [guide](), [incident](), [maintenance](), [override](), [scheduled](), [software-development](), [software-engineering]() ### AI overview This guide explains how feature flag overrides applied during incident response can accidentally become permanent, causing drift between production and staging, fragmented user experiences, and maintenance debt. It recommends scheduling automatic expiration when applying an override so users re-enter the rollout path after the underlying fix is deployed. ### Source excerpt I originally wrote this guide while working at Square to help my teams address a recurring problem: feature flag overrides applied during incident response were quietly becoming permanent, creating dr ## From Bash to Bliss: Scaling Vespa Operations with Temporal DevFeed: [From Bash to Bliss: Scaling Vespa Operations with Temporal]() Original publisher: [Read original article]() Author: Martynas Jakimčikas Published: 2026-01-21T00:00:00Z Content type: article Language: en Sources: [Vinted]() Topics: [Platform Engineering](), [Orchestration](), [Scripting, bash](), [Automation](), [health checks](), [upgrade]() Tags: [automation](), [commands](), [complexity](), [health-checks](), [maintenance](), [orchestration](), [platform](), [scheduled](), [script](), [self-service](), [upgrade]() ### AI overview This article describes how Vinted's platform team handled growing maintenance demands for its Vespa search infrastructure. As the environment expanded from hundreds to more than a thousand nodes and included many deployments, Bash scripts and Knife commands became difficult to manage. The team moved toward durable orchestration with Temporal, automated health checks, scheduled upgrades, and self-service guardrails. ### Source excerpt Growing platform - Growing maintenance Keeping the Lights On (KTLO) is an essential, yet often taxing, part of a platform engineer's role. It represents the routine operational work required to keep the business running and the platform stable. For our team, this primarily involves maintenance on our search engine, Vespa - ranging from version upgrades and service restarts to draining traffic from nodes for hardware replacements. ## How we Use Dagster Automations in our Data Pipeline DevFeed: [How we Use Dagster Automations in our Data Pipeline]() Original publisher: [Read original article]() Author: Delphine Rabiller Published: 2025-12-10T11:32:42Z Content type: article Language: en Sources: [FreeAgent]() Topics: [Automation](), [data](), [migration]() Tags: [analytics-engineering](), [automation](), [dagster](), [data-ml](), [data-pipeline](), [data-pipelines](), [declarative](), [migration](), [pipeline](), [scheduled](), [sensors](), [tooling](), [triggers]() ### AI overview This engineering post explains how FreeAgent is migrating data pipelines to Dagster and re-architecting its automation logic. It describes three approaches to automating asset materialization: schedules, declarative automation, and asset sensors, including when schedules are appropriate and how declarative automation uses asset dependencies and materialization status. ### Source excerpt Introduction The heart of a reliable data platform are robust and automated data pipelines. As our team migrates our data pipelines to Dagster, re-architecting our automation logic is a crucial task. Dagster offers condition-based approaches to creating or updating a data asset (table or file), moving us toward a modern, asset-centric view of data. This [...] ## UPI Autopay: Benefits and Use cases DevFeed: [UPI Autopay: Benefits and Use cases]() Original publisher: [Read original article]() Author: Joshua D'Costa Published: 2025-11-21T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service]() Tags: [automatic](), [bank](), [billing](), [card](), [india](), [payments](), [product](), [saas](), [scheduled](), [subscriptions](), [webhooks]() ### AI overview This tutorial explains UPI Autopay for SaaS and subscription businesses serving customers in India. It covers mandate creation and approval, scheduled or variable automatic debits, merchant setup, and notifications through webhooks. ### Source excerpt Understand UPI Autopay for SaaS subscriptions in India, including mandate flows, merchant setup steps, user benefits, and renewal success impact. ## BGP training course at NL-ix in Zoetermeer October 7 DevFeed: [BGP training course at NL-ix in Zoetermeer October 7]() Original publisher: [Read original article]() Published: 2024-07-15T09:54:40Z Content type: news Language: en Sources: [BGPexpert]() Topics: [BGP](), [Protocol (disambiguation)]() Tags: [bgp](), [course](), [dutch](), [gateway](), [information](), [learn](), [protocol](), [scheduled](), [training](), [work]() ### AI overview NL-ix is scheduled to hold a one-day BGP training course in Zoetermeer on October 7, led by Iljitsch van Beijnum. Participants will learn BGP internals, with instruction offered in English or Dutch according to participant preferences. ### Source excerpt NL-ix brings back its famous BGP (Border Gateway Protocol) course. The course is scheduled to happen on October 7. It will be conducted by Iljitsch van Beijnum. In one day (09.30 - 16.00) course participants will learn the internals of BGP protocol. This will help them with a much better understanding of their current BGP work. In English or Dutch depending on the wishes/needs of the participants. More information and registration. ## Announcing The Road To Devcon Grants DevFeed: [Announcing The Road To Devcon Grants]() Original publisher: [Read original article]() Author: Devcon Published: 2023-06-29T00:00:00Z Content type: news Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [.NET Conf]() Tags: [apply](), [community](), [conference](), [contribute](), [devcon](), [education](), [ethereum](), [events](), [scheduled](), [southeast-asia](), [university](), [workshops]() ### AI overview The Road to Devcon Grants initiative supports Ethereum events, grassroots communities, university clubs, workshops, and educational activities across Southeast Asia ahead of Devcon 7. Grants can provide up to $1,000, with smaller meetups encouraged. ### Source excerpt Devcon 7 is scheduled for 2024, and while the final location is still TBA, we can say one thing with certainty: Devcon is coming to Southeast Asia! 🌏 We can't wait for our journey to Devcon 7 in Southeast Asia to begin and are happy to see that the... ## Tinybird introduces Copy Pipes for scheduled data movement DevFeed: [Tinybird introduces Copy Pipes for scheduled data movement]() Original publisher: [Read original article]() Author: Tinybird Published: 2023-06-15T00:00:00Z Content type: release Language: en Sources: [Tinybird]() Topics: [data]() Tags: [data](), [product-updates](), [scheduled]() ### AI overview Tinybird introduces Copy Pipes, which automate data movement between sources and destinations and support scheduled transforms without custom scripts. ### Source excerpt Copy Pipes automate data movement between sources and destinations. Set up scheduled transforms without writing custom scripts. ## Simplifying event sourcing with scheduled snapshots in Tinybird DevFeed: [Simplifying event sourcing with scheduled snapshots in Tinybird]() Original publisher: [Read original article]() Author: Iván Malagón Published: 2023-03-02T00:00:00Z Content type: release Language: en Sources: [Tinybird]() Topics: [API](), [data]() Tags: [api](), [data](), [product-updates](), [scheduled]() ### AI overview Tinybird's Scheduled Copy API automates data movement according to a schedule, removing the need for manual triggers. ### Source excerpt The Scheduled Copy API automates data movement on your terms. No more manual triggers. Set it and let it run. ## Devcon VI Announces Ticket Auction and Raffle and Extends Speaker Application Deadline DevFeed: [Devcon VI Announces Ticket Auction and Raffle and Extends Speaker Application Deadline]() Original publisher: [Read original article]() Author: Devcon Published: 2022-06-28T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [.NET Conf](), [Ethereum]() Tags: [devcon](), [distribution](), [ethereum](), [events](), [payment](), [scheduled]() ### AI overview The article announces a pre-sale auction and raffle for Devcon VI tickets on Arbitrum, with ETH as the accepted payment method, and extends the speaker application deadline to July 5 at 23:59:59 UTC. ### Source excerpt Three weeks ago, we opened the speaker and volunteer applications as well as the discount builder and student tickets, and we are excited about the quality of submissions! This year, we've opened applications for those looking to attend Devcon with Builder and Student discounts, as [Speakers... ## Gray Glacier Upgrade Announcement DevFeed: [Gray Glacier Upgrade Announcement]() Original publisher: [Read original article]() Author: Tim Beiko Published: 2022-06-16T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Network](), [Blockchain](), [Protocol (disambiguation)]() Tags: [announcement](), [blockchain](), [developers](), [ethereum](), [network](), [node](), [protocol](), [protocol-announcements](), [scheduled]() ### AI overview Ethereum's Gray Glacier network upgrade was scheduled for block 15,050,000, expected around June 29, 2022. It delayed the Ice Age/Difficulty Bomb by 700,000 blocks, or roughly 100 days, and required node operators to update compatible clients. ### Source excerpt The Ethereum network will be undergoing a scheduled network upgrade at block 15,050,000, which is expected to occur on Wednesday, June 29, 2022. The exact date is subject to change due to variable block times and time zones. Please upgrade your node before Monday, June 27, 2022 to account for... ## Preventing WorkManager crashes when updating Android worker classes DevFeed: [Preventing WorkManager crashes when updating Android worker classes]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2022-04-27T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [Android](), [migration](), [App](), [implementation]() Tags: [android](), [background-work](), [blogs](), [crash](), [crashes](), [implementation](), [lifecycle](), [migrate](), [retry](), [scheduled](), [workmanager]() ### AI overview This tutorial explains how Android WorkManager can crash after an app update when pending work references a worker class that was removed, renamed, or moved. It discusses cancelling or migrating pending work and using a custom WorkerFactory. ### Source excerpt WorkManager is great to schedule background work on Android. However, since scheduled work lives outside of the app lifecycle, you might run into unexpected crashes. [Next page]()