Skip to content

A Schedule Per Channel

The free edition has one posting schedule for every channel. With UmbSocial Pro licensed, a channel can have its own slots, such as LinkedIn on Tuesday and Thursday mornings and Bluesky every day at noon.

Add to queue looks at the channels a post goes to:

  • A channel with its own slots uses them. A channel with none uses the shared schedule, so nothing changes for a channel you leave alone.
  • A post on several channels can go out in any slot any of them has: the candidates are the union of their slots, and the earliest free one wins.
  • A slot is taken when another scheduled post (not a draft) on any of the post’s channels is at exactly that time. A slot taken on one channel stays free for posts on other channels only.
  • As on the shared schedule, UmbSocial looks up to 28 days ahead, a post being queued again doesn’t take its own slot, and times are in the schedule’s time zone (a channel’s slots use the same one).
  • With no channel chosen yet, the answer is the shared schedule’s next free slot.

In Settings › UmbSocial › Schedule & writing, open the Per channel view. It has a box for each enabled channel with the same slot editor as the shared schedule. A channel with no slots shows a note that it uses the shared schedule. Edit the slots and press Save channel schedules in the footer bar: every channel’s schedule is saved, and a missing time is shown in the box it belongs to. The view and its button need the ManageSettings permission.

Behind the view is an API. A channel’s slots are a list of weekday and local time, to the minute, with the same rules as the shared schedule: duplicates are saved once, and there are at most 168 slots (schedule.too_many_slots). An empty list removes the channel’s own slots, and the channel uses the shared schedule again.

  • GET /umbraco/management/api/v1/umbsocial/pro/channels/{key}/schedule returns { "slots": [{ "day": "Monday", "localTime": "09:00:00" }] }.
  • PUT to the same address replaces the channel’s slots with the body, in that shape.
  • {key} is the channel’s key. An unknown or removed channel is 404 (channel.not_found).
  • Both need the ManageSettings permission, and UmbSocial must be licensed (licence.pro_required otherwise).
  • Saving a channel’s slots never changes the shared schedule or another channel’s slots, and changing slots doesn’t move posts that are already scheduled.

While UmbSocial isn’t licensed, Add to queue uses the shared schedule for every channel, the Per channel view is hidden, and the endpoints are refused. Nothing is deleted: the channels’ slots stay stored and work again when the licence is active.

Two notifications, in UmbSocial.Pro.Notifications:

Notification When Properties
SocialChannelScheduleSavingNotification Before a channel’s slots are saved. Change Target.Slots, or cancel it to refuse the save (channel_schedule.cancelled:<message>). ChannelKey, Target (SocialChannelScheduleDraft: Slots), Existing (the slots stored now).
SocialChannelScheduleSavedNotification After the slots were saved. ChannelKey and Slots (empty when the channel uses the shared schedule).

From code, a channel’s slots are IChannelScheduleService (UmbSocial.Pro.Scheduling): GetAsync and SaveAsync, with the same rules, notifications and codes as the endpoints. Pro’s services check the licence themselves, not only its endpoints: while UmbSocial isn’t licensed, a service that changes something refuses with licence.pro_required and changes nothing, and one that reads finds nothing.

The queue’s time comes from the ISlotFinder service. Pro replaces UmbSocial’s default finder with its own, but only when the default is the one registered: a finder your site registers wins over both.