EMAIL_CONTROL issue

[Plex134]

Good morning,
I'm having an issue in that the account_curve_report fails to send email with the account curve PDF, resulting in a blank email. In my logs I get

ERROR mongoDataWithMultipleKeys Failed to create compound index for collection 'EMAIL_CONTROL', check config: 'keys'

which I assume means that account_curve_report tries to create an index on report_type and timestamp, but the EMAIL_CONTROL collection uses type and datetime (e.g., type: "last_email_sent", datetime: 202510032302342880). I think this mismatch prevents metadata storage, causing the blank email. Other reports (e.g., Slippage report) work, using type/datetime (per commits 2466dfa, 9674f6e). Manual runs generate the PDF, but automated runs fail to email it.

I was going to try to create a MongoDB index on type and datetime to match the collection’s structure.

db.EMAIL_CONTROL.createIndex({ "type": 1, "datetime": 1 })

Does this seem correct? (sorry, I'm not terribly comfortable with this part of pysystemtrade)

Thanks,
-Plex

[bug-or-feature]

First have a look to see what the current index is/are. Mine says:

production> db.EMAIL_CONTROL.getIndexes()
[
  { v: 2, key: { _id: 1 }, name: '_id_' },
  {
    v: 2,
    key: { type: 1, subject: 1, datetime: -1 },
    name: 'type_1_subject_1_datetime_-1',
    unique: true
  }
]

That first one is just the default one you get for the id, that gets created automatically I think. PST code tries to create a multikey one as well, the config is in mongo_email_control.py lines 17 to 24 ish.

Try deleting the second one if it exists. Then, the next time you access that collection, the multikey index will be re-created

[Plex134]

Thanks Andy,
That worked.
The current index appeared the same as yours. I deleted it. When reports next ran, it was recreated and generated a PDF.