Delaying message broadcast

The best approach would be to publish the broadcast when the resource is available, after that one minute. What triggers the resource becoming available? Wherever that codepath is, is where you can hook in the broadcast. If it’s third-party processing, see if they support a post-back URL to your app, which you can then use to broadcast. Make sense?

Task.start(fn ->
  :timer.sleep(60*1000)
  PhoenixApp.Web.Endpoint.broadcast("channel_name", "xx_update", %{payload: %{id: 1} })
end)

but this is very hackish - you really want to broadcast directly when the publication is ready.. (as @chrismccord said..)

Hey @chrismccord thanks for you time!

Your approach it’s the best way to solve the problem, but unfortunately, it’s a third party service that can’t provide me a callback or something like that.
Actually I use the approach that @outlog shared here, but with this kind of solution, whole process still blocking until the sleeps time end.

??? The process which calls Task.start does not block, and I don’t see how the blocking inside of the task could possibly matter, since it’s not visible to anything.

@sribe My bad! We are using :timer_sleep in a very very bad way here

We are using it without a Task.start, so, that’s why we getting a blocking(long time waits) to return something trough publication creation API calls

I’ll adjust the code to fit the example and probably this will solve our issue