Sentio Docs
Search
⌃K
👋
Welcome to Sentio
🔗
Setup
🗄
Samples
💡
Quickstart
How-to Guides (by examples)
➡
Adding ABIs
➡
Data collection
➡
Visualize results
➡
Create alerts
➡
Share your project
Developer Guides
➡
CLI Reference
➡
SDK Guide
Access Sentio Via APIs
Sentio API
References
✅
How Sentio Works
🖥
Concepts
▶
UI layout
🔒
Quotas and Limits
💎
Supported Networks
🤝
Permission and Sharing
Best Practices
🔍
Best Way To Manage nodejs
🔍
Multi-Chain Support
🔍
Avoid High Cardinality
🔍
Updating Processors
🔍
Handling Errors
🔍
Performance Tuning
🔍
Cost Reduction
🔍
How To Handle Proxy Contracts?
🔍
Upgrade SDK Version
🔍
Processor State and Execution Order
🔍
Formula usage best practices
Powered By GitBook
🔍

Updating Processors

It is quite common for users to update your processor code. To update it, simply rerun the upload command.
yarn sentio upload
Our system will re-run all the historical data and update your metrics.
This means that it will erase the historical data, and your usage will be interrupted. Our paid users can use Version Control (Only available for Paid Users)to avoid downtime.
Best Practices - Previous
Avoid High Cardinality
Next - Best Practices
Handling Errors
Last modified 3mo ago
Copy link