List of read/write positions of sources and destinations for this bot
For local dev it will ignore the cron locking and force it to run (will run through the handshake and force it to take the lock)
The ID of the bot
For local dev, skip the locking process altogether for guaranteing only one instance of the bot runs
The instance ID of the bot, used for fanout. So, if running multiple instances of the same bot we can tell which this is.
The name of the bot
The invocation timestamp token which is what is used to lock on to prevent multiple concurrent invocations to the same bot
Generated using TypeDoc
First, remember that for legacy reasons
Cron
really meansBot
. This is details about a bot.