p202 forecast-event create

Create a new forecast-event

Writessupports --staged
All commands

p202 CLI reference

Back to the docs

01Run it

Straight from the command's own help.

p202 forecast-event create --event-name <event_name> --event-date <event_date> --json

02What you get

Captured from the real binary, run against a demo store with 30 days of traffic. Switch tabs to see the same run as JSON, the shape scripts and agents parse.

p202 forecast-event create --event-name "Spring Sale" --event-date 2027-03-20 --impact-type boost --expected-impact-pct 60
$ p202 forecast-event create --event-name "Spring Sale" --event-date 2027-03-20 --impact-type boost --expected-impact-pct 60
end_date:             
etag:                 "3ba059d1a21922b5da52b87896ea3cca3e4dd5bf"
event_date:           2027-03-20
event_id:             2
event_name:           Spring Sale
expected_impact_pct:  60
impact_type:          boost
lag_days:             0
lead_days:            0
notes:                
recurrence:           none
tags:                 
user_id:              1
version:              3ba059d1a21922b5da52b87896ea3cca3e4dd5bf
Real output · p202 1.9.77 · demo dataexit 0

03Build your command

Pick values and the command line writes itself, quoted and ready to paste.

p202 forecast-event create

Set flags below; the command updates as you type.

04Flags

11 flags, plus the global flags every command takes.

FlagWhat it does
--end-datestringEnd date for multi-day events (YYYY-MM-DD)
--event-datestringrequiredEvent date (YYYY-MM-DD) (required)
--event-namestringrequiredEvent name (e.g. 'Black Friday', 'Server Outage') (required)
--expected-impact-pctstringExpected impact percentage (e.g. +200 for 3x boost, -50 for half)
--idempotency-keystringRetry-safe create: the server records the response under this key and replays it on a retry with the same key and payload instead of creating a duplicate
--impact-typestringImpact type: boost, suppress, neutral
boostsuppressneutral
--lag-daysstringDays after event that impact decays
--lead-daysstringDays before event that impact ramps up
--notesstringFreeform notes
--recurrencestringRecurrence: none, monthly, yearly, custom
nonemonthlyyearlycustom
--tagsstringComma-separated tags (e.g. 'us-holidays,retail')

05For agents

Running this from an agent

  • Read the same facts as JSON: p202 commands forecast-event create --json.
  • With AI_AGENT, CLAUDECODE or another agent variable set, output is compact JSON and errors arrive on stderr as a JSON envelope with a hint.
  • Exit codes: 0 ok, 1 bad input, 2 auth, 3 network, 4 server error, 5 partial failure.
  • This command writes. Add --staged to record it as a proposal a person applies with p202 change apply.
p202 commands forecast-event create --json
{
  "path": "p202 forecast-event create",
  "use": "create",
  "short": "Create a new forecast-event",
  "runnable": true,
  "example": "p202 forecast-event create --event-name <event_name> --event-date <event_date> --json",
  "flags": [
    {
      "name": "end-date",
      "type": "string",
      "default": "",
      "usage": "End date for multi-day events (YYYY-MM-DD)",
      "required": false
    },
    {
      "name": "event-date",
      "type": "string",
      "default": "",
      "usage": "Event date (YYYY-MM-DD) (required)",
      "required": true
    },
    {
      "name": "event-name",
      "type": "string",
      "default": "",
      "usage": "Event name (e.g. 'Black Friday', 'Server Outage') (required)",
      "required": true
    },
    {
      "name": "expected-impact-pct",
      "type": "string",
      "default": "",
      "usage": "Expected impact percentage (e.g. +200 for 3x boost, -50 for half)",
      "required": false
    },
    {
      "name": "idempotency-key",
      "type": "string",
      "default": "",
      "usage": "Retry-safe create: the server records the response under this key and replays it on a retry with the same key and payload instead of creating a duplicate",
      "required": false
    },
    {
      "name": "impact-type",
      "type": "string",
      "default": "",
      "usage": "Impact type: boost, suppress, neutral",
      "allowed_values": [
        "boost",
        "suppress",
        "neutral"
      ],
      "required": false
    },
    {
      "name": "lag-days",
      "type": "string",
      "default": "",
      "usage": "Days after event that impact decays",
      "required": false
    },
    {
      "name": "lead-days",
      "type": "string",
      "default": "",
      "usage": "Days before event that impact ramps up",
      "required": false
    },
    {
      "name": "notes",
      "type": "string",
      "default": "",
      "usage": "Freeform notes",
      "required": false
    },
    {
      "name": "recurrence",
      "type": "string",
      "default": "",
      "usage": "Recurrence: none, monthly, yearly, custom",
      "allowed_values": [
        "none",
        "monthly",
        "yearly",
        "custom"
      ],
      "required": false
    },
    {
      "name": "tags",
      "type": "string",
      "default": "",
      "usage": "Comma-separated tags (e.g. 'us-holidays,retail')",
      "required": false
    }
  ]
}