Make your Slack a little more Prefect: #2F383F,#4D606E,#EBF0F3,#3B8DFF,#4D606E,#FFFFFF,#27B1FF,#FE5196

Hi everyone <!here>! Prefect 0.6.0 has been released, and includes many new features, integrations and bug fixes, including: - ability to share caches across tasks and flows - new Prefect CLI (credit to @josh) - improved dask integrations including better dask UI experience + ability to hook into dask worker resources via Task tags Check out our announcement with some additional details here: https://medium.com/the-prefect-blog/announcing-prefect-0-6-0-cloud-ready-907a97d4b6fa

Hi <!here>! We just released a new way to build flexible schedules in Core master, a few details are in this blog post: https://medium.com/the-prefect-blog/custom-schedules-in-prefect-ac638a1945f8. Please check it out!

Hi everyone <!here>! This channel’s been quiet for too long and we’re bursting at the seams over here. First up — we just relaunched https://www.prefect.io. It’s hard to believe how far the old website got us, in all honesty, but it’s time to take a big step forward. In the near future we’ll be adding a lot more to the site in the way of posts, use cases, tutorials, etc. etc. that we’re developing with Cloud partners.

Some of you may notice something that we’ve hinted at but haven’t discussed in public yet — Prefect Scheduler, which is a completely free version of our enterprise Prefect Cloud. https://www.prefect.io/products/cloud-scheduler

As early adopters of Core, we hope those of you in the Slack community will be some of the first to get access to Scheduler (or Cloud!) Please sign up and let us know so we make sure our team gives you priority. If you have any questions whatsoever, contact myself, @Chris White, or any of the other Prefect team members here.

Hello everyone! The Scheduler announcement is live, so hopefully those of you in this chat have had a chance to join the waitlist as it is already starting to grow: https://medium.com/the-prefect-blog/a-scheduler-for-the-internet-fd706336e2fe

Hello everyone <!here>! Prefect Core 0.7.0 is out and includes many improvements, especially for our Cloud users. Check out our announcement here: https://twitter.com/markov_gainz/status/1189555300841345025

Hello everyone <!here> - the ability to invite new team members to your tenant from the UI is now live 🚀 Simply visit your Team > Members page and invite away; invitees can expect an email from

<mailto:prefect@prefect.io|prefect@prefect.io>

with a link to accept. Note that brand new users will need to click “Sign up” on the Auth0 login screen to create an auth0 account

Hey everyone <!here>! We’ve been quietly working on a much simpler and faster way to get your Cloud flows up and running that we’d really like some beta testers for. If you’re interested, please DM me and I’ll add you to the preview group. Note that this will require a Cloud account of some kind, so if you’re not in our free Scheduler tier yet I can fast track you on the waitlist!

Hi <!here> - a new version of the Cloud UI was just released! The UI team has been hard at work improving the process of flow management; this release includes a new and much-requested feature: the ability to restart failed task-runs from the UI! Now when your flows fail at a specific task, you don't have to kick off a new flow run... instead, simply select the failed task and restart the flow run from that point.

Hi Prefect Community - a new version of the Cloud UI was just released! New Features: • Adds a “Mark As” button on the task-run page to enable changing the state of a task-run • Adds a “Mark As” button to the flow run page to enable changing the state of a flow run • Updates the Playground, now called the Interactive API, to include a full schema explorer • Add a comprehensive JSON editor for setting flow run parameters Enhancements: • Add helpful Drawer when the “Run” button is pressed for flows which are archived Fixes: • Fixes disabled state for the “Restart” button on the Flow Run page • Fixes a bug where mutation requests sent via the Interactive API weren’t formatted correctly

If you’re interested in joining the Beta for the Interactive API, shoot me a message!

New blog post by @Jenny on an incredibly clever use case of Prefect for efficient remote A/C control!! Check it out the details here: https://medium.com/the-prefect-blog/my-prefect-home-c05ebe625410

<!here>; v0.2.0 of the UI has been released and includes two exciting and highly-anticipated features! 1️⃣ The Interactive API is leaving beta! The Interactive API is a first-class way to use the Prefect Cloud GraphQL API: • interact directly with your Prefect data from the UI without having to worry about tokens or endpoints • leverage schema lookahead and GraphQL validation to construct powerful queries directly in the browser • easily search and traverse the GraphQL schema

2️⃣ Cancel ALL the flow runs! You can now save time and free up valuable resources by cancelling any flow running on Prefect Core 0.7.3 or greater

Have questions? Want to check out Prefect Cloud? Feel free to send me a message!

<!here> Prefect 0.8.0 is out! The headline of this release is the highly anticipated Universal Deploy feature, which allows you to store your Flows in non-Docker storage environments (including locally, Azure, S3 and GCS) and orchestrate them with Prefect Cloud! Check out our blog post describing the changes here: https://medium.com/the-prefect-blog/introducing-prefect-universal-deploy-7992283e5911

Hi everyone <!here> - Prefect 0.8.1 is already out! It includes many polishing features inspired by all the great feedback we received on 0.8.0. Checkout the Changelog here: https://github.com/PrefectHQ/prefect/releases/tag/0.8.1 For all of you heavy Dask users out there, Prefect 0.8.1 + updates to Prefect Cloud now allow for toggling various settings on a per-flow basis, including: - the ability to turn off heartbeats - the ability to turn off state version locking to allow Dask to rerun your tasks as needed For more information, check out the API documentation for Flow Settings here: https://docs.prefect.io/cloud/concepts/flows.html#flow-settings Thanks to everyone for your continued engagement and feedback - happy engineering!

<!here> Hey everyone ー My name is Lauren and it's my first week as a Product Designer at Prefect. We are embracing user research to drive feature definition and prioritization. As members of the community, we'd love to let you see early concepts of what we're working on to get your feedback.  If you're interested in helping us create the best tool, fill out this one minute survey and we'll follow-up with you soon! https://forms.gle/a6hdNusPbAawc7pi7

<!here> New Year, New Prefect Core! We released 0.9.0 earlier today which includes improved Agent/Flow configuration through environment variables as well as more sensible defaults for Result Handlers - check out our blog post on some of the larger features here: https://medium.com/the-prefect-blog/prefect-0-9-0-unlocking-cloud-27e05a96e52a

<!here> Happy New Year Prefect Community! As many of you are aware, Prefect is growing rapidly. As a part of that growth we are looking for experienced Solutions Engineers to join the team, and what better forum to reach out to than our own user community! If interested, please see the attached job description and send me an email directly to further explore (david@prefect.io)

<!here> We're experiencing some downtime with the Cloud API; we're working to resolve the issue and will update as soon as we can.

Hi <!here>, update on the recent brief Prefect Cloud API outage. While improving our infrastructure, we experienced a disruption which resulted in the system being unable to launch new flow runs (including those that were scheduled to run) or to successfully set states. The disruption lasted from 18:36 EST to 18:53 EST. Ultimately, any scheduled work was slightly delayed, but flows which began running prior to the outage may need to be re-run. We've taken steps to ensure the health of our system and to prevent this issue moving forward. We apologize for the inconvenience - if you have any questions, feel free to message me.

<!here> Hi Prefect Cloud users! As part of an effort to make our infrastructure and deployments more robust, we'll be performing some scheduled maintenance this Sunday afternoon. We anticipate scheduled runs during this window to run late, but all flows running before and during this window should run to completion as expected. Please feel free to reach out with any questions.

For anyone following along at home, our maintenance has been successfully completed! You should see your flow runs resuming their scheduled behavior.

Hi <!here>; I wanted to take a minute to update you on some big improvements hitting Prefect Cloud 😛refect-cloud: today! Some of the highlights: ❌ Errors: Cloud is now surfacing errors more readily; one of the big pieces of feedback we've been hearing has been around time to action and how our platform can best facilitate quick iteration in response to flow runs that are not behaving as expected. We think that surfacing individual logs and linking to those directly will help speed this process and let you know if things are awry sooner. 🤖 Agents: we're displaying general information regarding agents; exposing the number of agents you have querying Cloud, their labels, and the last time we've heard from them should help you diagnose and address critical infrastructure problems much more quickly than before. 🌐 Navigation and usability: the number of features in Cloud has grown a lot over the last few months; we heard from a number of users that feature discoverability and navigation between pages was not ideal. To address this, we redesigned the navigation and organization of the various dashboard from the ground up, to help you understand at a glance the actions, information, and relationships available within any given scope (be that system-wide, project, flow, etc.), and provide the scalability our platform needs to ensure you're able to fully leverage all the great new features the Prefect team is hard at work building. If you have any feedback or concerns, don't hesitate to reach out to me!