Best approach for this IMO would be to create a Custom Object to query, and schedule based on that. @matthew_lind, does that track? I don’t have much experience with creating objects, but the big win there is that you could create the object with the bare minimum of information, and merge it as needed in the query to get updated company or user info. And that way you could update the object monthly as needed without having to change the synced CSV.

I’m not sure whether scheduling a recurring send on a CSV source is possible.

Thanks @dayn.johnson , and a friendly wave toward @mradford.

I’m not a 100% expert on this, having never attempted to schedule something recurring with a CSV source. And I generally avoid CSVs as sources, favoring logical queries where possible (perhaps now for even one more reason.)

However, I’m not surprised the scheduling option goes away with a CSV source. Because CSVs are generally used for use cases involving one-time Participant loads, I wouldn’t typically schedule a Program to re-query a CSV periodically.

Hi @matthew_lind  We do have unique situations where we have a set of contacts that can’t be selected via query and that csv list doesn’t change often. But, we can continue to run the program once, stop and clone it if there is no scheduling option. Just wanted to make sure I wasn’t missing an option for this. 

@mradford The suggestion for scheduling on a custom object would probably work out.

What I’ve done in similar situations is upload my CSV to our Gainsight S3 bucket, then pull that into a data design that I can run manually if I need to update that CSV (after replacing the copy in S3 first). Make sure that data design is set up to be a Universal Data Space so you can query it from your JO, then in theory you should be able to schedule your JO to pull from that data space monthly to send those outreaches.