Upstash Documentation

FUNCTION KILL

Kill a running function.
2 min read

Use FUNCTION KILL to stop a function that is currently running and has not yet written anything.

A function that has already modified data cannot be killed, because stopping it halfway would leave the dataset in a state that no atomic step could produce. Check FUNCTION STATS to see whether a function is running before calling this.

The current Upstash deployment recognizes the command but has no interruptible running-function state to act on, so it replies with a NOTBUSY error.

Syntax#

Arguments#

This command takes no arguments.

Important points#

  • The current deployment recognizes this command but reports NOTBUSY because it does not expose an interruptible running-function state.

Response#

The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.

ProtocolReply
RESP2Error reply (NOTBUSY on the current deployment)
RESP3Error reply (NOTBUSY on the current deployment)
Note

Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.

Examples#

TCP examples use the TLS REDIS_URL from the Upstash console. REST examples use UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN.

Redis CLI
@upstash/redis
Note

This command is not supported yet in @upstash/redis.

upstash_redis
Note

This command is not supported yet in upstash_redis.

ioredis
node-redis
redis-py
go-redis
jedis
redis-rs