I wanted to ask if anyone knows the best Api.ai entity to describe a duration with different ways.
Example:
Do the task in 30 min
Do the task in 1 hour and 30 min
Do the task from 1:10 pm to 2:20 pm
Unfortunately the #sys.duration entities takes only one unit and #sys.periode doesn't respond to the first two examples.
Thanks!
Related
Are there any expiration period for this Power Automate - Approvals when the user taking more time to submit the decision?
I tried with some trial data but, need to get an idea from an experienced person.
Flows have a timeout period of 30 days.
You can refer to this documentation for more information.
https://learn.microsoft.com/en-us/power-automate/limits-and-config#duration-limits
If your approval is likely to run for more than 30 days, read this article.
https://learn.microsoft.com/en-us/power-automate/modern-approvals#create-long-running-approvals
The ice_cube gem, meant to handle recurring events, allows to set a start_time, as well as a duration, when creating a schedule, as follows:
schedule = IceCube::Schedule.new(start_datetime, duration: duration)
Then, we can add recurrence rules to that schedule, for instance like this:
schedule.add_recurrence_rule(IceCube::Rule.daily)
This is great when you want to create an event of the same duration for every occurrence, such as a standup meeting that starts at 9:00am and lasts 15 minutes every day of the week.
However, what if that standup meeting needs to be 30 minutes on Tuesdays, and 15 minutes every other day of the week?
I can see how we could accomplish that with two different schedules:
schedule1 = IceCube::Schedule.new(start_time, duration: 900)
schedule1.add_recurrence_rule(IceCube::Rule.weekly(self.weekly_frequency).day(:monday, :wednesday, :thursday, :friday))
schedule2 = IceCube::Schedule.new(start_time, duration: 1800)
schedule2.add_recurrence_rule(IceCube::Rule.weekly(self.weekly_frequency).day(:tuesday))
However, is there a way to accomplish this with just one schedule, by specifying start_time and duration at the rule level instead of at the schedule level?
If this can be achieved only with multiple schedules, is there a way to check if an event (like the standup meeting in my example) occurs based on the rules of multiple schedules?
How do I make the Jfxtras Agenda component treat the following two appointments as non-overlapping? Also, is there a way to increase the snap-to-grid granularity of the grid from 5 minutes to 30 minutes, to mimic Outlook? With the 5 minutes precision, it is very difficult to create back-to-back appointments, without making them overlap, or creating gaps between them.
Appointment 1
Start: 2pm
End: 5pm
Appointment 2
Start: 5pm
End: 9PM
I fixed the consecutive appointments rendering issue, the new snapshot should work ok. As for the rounding, I will add a CSS stylable property where this can be set later today.
I simply modified the appointment callback. To make it so that only 15 minute segments could be used to make appointments I used dateTimeRange.getStartLocalDateTime().minusMinutes(dateTimeRange.getStartLocalDateTime().getMinute()%15)
You can use this for the end time as well, and from then on you will only get appointments made with 15 min intervals. Just change the 15 to change the interval. The only potential downfall is that you could frustrate users if they shoot too low when dragging, but that could be solved as well with a simple if statement.
I've been trying to create notifications that happen on a weekly basis - for example, every monday at 8am.
I've tried to use a recurring toast for this - http://msdn.microsoft.com/en-us/library/windows/apps/hh465417.aspx - but realized that the recurrence parameters are more designed for a snooze functionality, with a maximum delay of 60 minutes, and a maximum repeat for 3 times.
Is there a suggested workaround for this?
Is there a best practice for such a use case?
Thanks!
You're right that the recurrence on scheduled toasts is designed for snooze. Unfortunately, the API doesn't provide a way to show the same toast multiple times on a fixed schedule.
You'll need to manually create a ScheduledToastNotification each time you want it to be shown. In your example, you might create and schedule out a toast a week for each Monday at 8 AM.
I am getting 500 HTTP error on some random requests when 8 threads creates tasks.
Error messages are funny:
25 tan reindeer cheer equally
10 sad sharks rush well
Please let me know what is the best way for fast (parallel) task creation.
Can you give us examples of tasks where it failed? It could be related to follower/assignee, esp. by email.