tencent cloud

Tencent Cloud Distributed Cache (Redis OSS-Compatible)

Release Notes and Announcements
Release Notes
Announcements
User Tutorial
Product Introduction
Overview
Product Strengths
Use Cases
Storage Engine
Product Series
Product Versions
Specifications and Performance
Read/Write Separation
Multi-AZ Deployment
Regions and AZs
Terms
Service Regions and Service Providers
Purchase Guide
Billing Overview
Pricing Center
Instance Purchasing
Renewal (Yearly/Monthly Subscription)
Refund (Yearly/Monthly Subscription)
Overdue Payments
Switching from Pay-as-You-Go to Yearly/Monthly Subscription
Getting Started
Quickly Creating an Instance
Connecting to Redis Instance
Operation Guide
Operation Overview
Connecting to a Database Instance
Managing Instances
Upgrade Instance
Management Node (Redis/ValKey Edition)
Multi-AZ Deployment Management
Backup and Restoration
Managing Accounts
Parameter Configuration
Slow Query
Access Management
Network and Security
Monitoring and Alarms
Event Management (Redis/ValKey Edition)
Data Migration
Global Replication for Redis Edition
Database Audit
Performance Optimization
Sentinel Mode
Development Guidelines
Naming Rules
Basic Usage Guidelines
Design Principles of Key and Value
Command Usage Guidelines
Design Principles of Client Programs
Connection Pool Configuration
Command Reference
Command Reference Overview
Redis Edition and Valkey Edition Command Compatibility
Version Command Usage Differences
Differences Between the Proxy Architecture and Direct Connection Mode
More Command Operations (Redis/Valkey Edition)
Memcached Edition Command Compatibility
Practical Tutorial
Building TencentDB for Redis® Client Monitoring Based on Spring Boot
Redis Client Connection Configuration Policy and Practice
Global SCAN Guide for Cluster Architecture
Eliminating Instances Securely
Hot Key and Big Key
AZ Migration Scheme
Troubleshooting
Connection Exception
Exception Analysis and Solution of Redisson Client Timeout Reconnection
Performance Troubleshooting and Fine-Tuning
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Parameter Management APIs
Other APIs
Backup and Restoration APIs
Region APIs
Monitoring and Management APIs
Log APIs
Data Types
Error Codes
FAQs
General
Connection and Login
Purchase
Service Agreement
Service Level Agreement
Terms of Service
Glossary
Contact Us

Modify Event Execution Plan

PDF
Focus Mode
Font Size
Last updated: 2026-03-17 18:10:56
In event management, you can flexibly and reasonably schedule the execution time of events based on actual business situations and the severity and urgency of Ops events, ensuring the efficiency and accuracy of Ops work while minimizing the impact on business.

Version Description

Tencent Cloud Distributed Cache Redis 4.0, 5.0, 6.2, and 7.0 editions, as well as Valkey 8.0 edition standard architecture and cluster architecture instances, support event management whether deployed in a single AZ or multiple AZs.

Prerequisites

Instance running status: Running.

Operation Steps

2. In the left sidebar, select Event Management.
3. On the right Distributed Cache (Redis-compatible) - Event Management page, select a region from the dropdown list at the top.
4. In the event list of Event Management, select the event that needs modification.
5. Click Modify Execution Plan in the Operation column.
6. In the Modify Execution Plan window, review the impact of executing this event, confirm the instance information, modify the start date in Modify Start Date, and reselect the start time and end time for the event execution plan in Modify Time Window.
Note:
Events with a Critical level cannot have their start dates modified; events with Critical or Important levels cannot have their execution canceled.
The Latest Start Date refers to the latest permissible start time for an event. Exceeding this time may adversely impact the overall plan. The modified plan start date cannot be later than the Latest Start Date.
After the start time is selected in the Modify Time Window, the end time can only be set within 30 minutes, 1 hour, 1.5 hours, 2 hours, or 3 hours after the start time.
7. Click OK, wait for the task to complete, and you can view the modified event information. For details, see Viewing Pending Events.

Related APIs

API
Feature Description
Querying Event Information
Modify Event Maintenance Time Window


Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback