Transactions with zero values for all pillars in the Airtable Growth Base are causing the Solana smart contract to fail with a panic. This issue results in failed transactions, preventing updates in Airtable, and causing the schedule processor to pick up and re-attempt the transactions.
Description
Transactions with zero values for all pillars in the Airtable Growth Base are causing the Solana smart contract to fail with a panic. This issue results in failed transactions, preventing updates in Airtable, and causing the schedule processor to pick up and re-attempt the transactions.
Initiate a transaction with zero values for all pillars in the Airtable Growth Base.
Observe the panic in the smart contract.
Expected Behavior
The smart contract should handle transactions with zero values gracefully, without panicking.
Additional Information
Solana Version: [Specify the version, if known]
Airtable Integration: [Specify any specific details about the integration]
Impact
This issue impacts the reliability of the smart contract, leading to failed transactions and preventing updates in Airtable. It also triggers the schedule processor to re-attempt the transactions.
Possible Solution
Web services and contract both should mitigate this condition
Description
Transactions with zero values for all pillars in the Airtable Growth Base are causing the Solana smart contract to fail with a panic. This issue results in failed transactions, preventing updates in Airtable, and causing the schedule processor to pick up and re-attempt the transactions.
Description
Transactions with zero values for all pillars in the Airtable Growth Base are causing the Solana smart contract to fail with a panic. This issue results in failed transactions, preventing updates in Airtable, and causing the schedule processor to pick up and re-attempt the transactions.
Error Details
Steps to Reproduce
Expected Behavior
The smart contract should handle transactions with zero values gracefully, without panicking.
Additional Information
Impact
This issue impacts the reliability of the smart contract, leading to failed transactions and preventing updates in Airtable. It also triggers the schedule processor to re-attempt the transactions.
Possible Solution
Web services and contract both should mitigate this condition
Attachments
https://explorer.solana.com/address/97d8t22JenPAwR85PZEXvc4gkvtAMZR9Ct7xuY11a2X8
Reproduction Environment
Production