Skip to main content
Solved

Schedules not saving in Data Designer?

  • February 14, 2023
  • 5 replies
  • 49 views
S

I love data designer, I’m seeing some inconsistency with the way it saves recurring schedules. Yesterday this list looked like it didn’t have schedules set. I went in to the designs (which had recurring schedules saved when I got to the page), I disabled the schedule, re-enabled it, then checked the listing again, and it showed a next run time instead of not scheduled. Engagement Score is an example of this behavior:

I go in this morning and my schedules have once again disappeared. 

I’ve confirmed that these Designs don’t refresh their data if they don’t have a next run scheduled appearing in the listing (even though there is one saved). 

 

Any of you other data designers out there seeing this? Also, I really wish that when you applied columns to the design rule (like Next Run) that they stuck, I have to set that every time and it’s valuable info. I’d also like last run, but I can get that in the execution history if I need to.

 

Best answer by matthew_lind

@Scotty at Calendly I would look at the End Date, labeled as “Till Date” in the UI.

If you have a schedule but the “Till Date” is in the past, then there is no future or next scheduled run. Even though you have a schedule, that schedule isn’t configured to trigger, and the DD listing then states “Not Scheduled”, which is partially true, but not the whole story as you note.

I’m noting in your last 2 screenshots that the DD you report as behaving mysteriously has a “Till Date” in the past.

alizee

5 replies

S
  • Scotty at Calendly
  • Author
  • Contributor ⭐️⭐️⭐️⭐️
  • February 17, 2023

This happened again. I took this screenshot this morning:

@Alicia Azar this is pretty critical to our operations, can you help me chase down what’s going on?

alizee
Forum|alt.badge.img+13
  • alizee
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • February 17, 2023

@Scotty at Calendly Can confirm I’ve never faced that issue. Can you share a screenshot of how your successfully scheduled designs looks like compared to the ones that seemingly unschedule themselves?

The most expensive part of building is the mistakes. That's true in construction. Not so much in CSOps. So ask questions, make mistakes and learn. All views expressed here are my own.
S
  • Scotty at Calendly
  • Author
  • Contributor ⭐️⭐️⭐️⭐️
  • February 17, 2023

Hey @alizee! Thanks for your reply, here are some screenshots, but for the life of me I can’t see any correlations.

Rule that says it is not scheduled even though it has configuration:

Rule that is configured for a schedule and the schedule is working:

The only difference I see is the email notification switch, I tried toggling that, no dice.

matthew_lind
Forum|alt.badge.img+11
  • matthew_lind
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • Answer
  • February 17, 2023

@Scotty at Calendly I would look at the End Date, labeled as “Till Date” in the UI.

If you have a schedule but the “Till Date” is in the past, then there is no future or next scheduled run. Even though you have a schedule, that schedule isn’t configured to trigger, and the DD listing then states “Not Scheduled”, which is partially true, but not the whole story as you note.

I’m noting in your last 2 screenshots that the DD you report as behaving mysteriously has a “Till Date” in the past.

Making people their best....currently disguised as a CS Ops Architect. How can I contribute to your success?
alizee
S
  • Scotty at Calendly
  • Author
  • Contributor ⭐️⭐️⭐️⭐️
  • February 17, 2023

Oh snap. Good eye! Should that be ‘Til Date?

Adding those dates now, I think I assumed the pattern was “pick the date and that’s it” instead of “pick the date, press return, then save”.

matthew_lind
Terms & ConditionsCookie settingsAccessibility statement