abelanger5

Results 57 comments of abelanger5

Hey @NikeNano, closing this for now, if we were to implement a reassign backoff we could potentially take advantage of the new `v1_retry_queue_item` table, but there have been quite significant...

Hi, we're not currently reviewing PRs that clearly contain AI-generated code. Thanks!

Hey @AndryHTC and @sh1man, I'm struggling to find where we've documented a docker-compose file with `/hatchet/hatchet-backend` as the command. It looks like replacing `/hatchet/hatchet-backend` with `/hatchet/hatchet-api` would fix it. Could...

Hi @1am, this can be set from the client side by added a key called `dedupe` to the [additional metadata](https://docs.hatchet.run/home/features/additional-metadata) of the workflow, and then setting the value to the...

Closing as we're pursuing a different docs overhaul

Hey @Apkahym, our cron syntax only supports minute granularity, it doesn't support seconds. One way around this is to create a parent workflow which runs every minute which spawns new...

Hey @joaopjoaquim, sorry for missing this. I'm closing this for now due to staleness, but feel free to rebase from main and reopen, and we could give it another look!

Hey @mxnoob, I think you're looking for `workflow_run_get`. For example: ```py run = hatchet.admin.run_workflow("MyWorkflow", {}) await run.result() workflow_run = await hatchet.rest.aio.workflow_run_get(run.workflow_run_id) # can now access workflow_run.status ```

Hey @mxnoob how are you instantiating the Hatchet client? This looks like potentially a configuration issue or a bug on our end -- it may be that when you overwrite...

Got it, I believe this is a bug on our end -- when you use the `HATCHET_CLIENT_HOST_PORT` variable, we are no longer setting the API server URL. As a quick...