James Ritchie
d6786002b2
* tasks no longer inside a group in the side menu (and added “cron”) * Delay using a timezone * Added React Not Defined error to the troubleshooting page * Improved the React common problem * Link to v2 docs * New Development section and entry in Common Problems * Concurrently running the terminal * Fixed the .env weirdness * Added section on creating PATs for Github actions * Improved the Machine spec and limits page * Quick start steps now have nice images * Added a diagram for the lifecycle functions * Added note about onFailure * CRON -> cron/Cron * WIP adding more steps to the next.js guide * WIP next.js * WIP adding tabbed steps for pages/app router * References to Infisical links to their homepage so it’s clearer * WIP updating the nextjs guide * WIP nextjs guide * More nextjs guide steps * More copy * Added rate limit trouble shooting * Removed old prisma error title * Added secret key step * Added a note for logging in using a specified domain if self hosting * typo * App router docs copy * Deploy copy update * Added a favicon.png to fix a docs build error * Removed unused snippet * Server actions now inside a tab * Server actions + restructured the triggering section * Added troubleshooting snippet for react event handlers * Added a new troubleshooting snippet for ESM * Updated old replaying image to reflect the new UI * Removed references to reattempting * Updated replaying from the run page * Added a bulk replay section * Updated the writing tasks intro page * Removed edge runtime code for now * Added edge runtime – it seems to just work! * import type
70 lines
2.5 KiB
Plaintext
70 lines
2.5 KiB
Plaintext
---
|
|
title: "Replaying"
|
|
description: "A replay is a copy of a run with the same payload but against the latest version in that environment. This is useful if something went wrong and you want to try again with the latest version of your code."
|
|
---
|
|
|
|
### Replaying from the UI
|
|
|
|
<Tabs>
|
|
<Tab title="From a run">
|
|
<Steps>
|
|
<Step title="Click the Replay button in the top right">
|
|
|
|
</Step>
|
|
<Step title="Confirm replay settings">
|
|
You can edit the payload <Icon icon="circle-1" iconType="solid" size={20} color="F43F47" /> (if available) and choose the environment <Icon icon="circle-2" iconType="solid" size={20} color="F43F47" /> to replay the run in.
|
|
|
|
|
|
</Step>
|
|
</Steps>
|
|
</Tab>
|
|
<Tab title="Runs list">
|
|
<Steps>
|
|
<Step title="Click the action button on a run">
|
|
|
|
</Step>
|
|
<Step title="Click replay"></Step>
|
|
</Steps>
|
|
</Tab>
|
|
</Tabs>
|
|
|
|
### Replaying using the SDK
|
|
|
|
You can replay a run using the SDK:
|
|
|
|
```ts
|
|
const replayedRun = await runs.replay(run.id);
|
|
```
|
|
|
|
When you call `trigger()` or `batchTrigger()` on a task you receive back a run handle which has an `id` property. You can use that `id` to replay the run.
|
|
|
|
You can also access the run id from inside a run. You could write this to your database and then replay it later.
|
|
|
|
```ts
|
|
export const simpleChildTask = task({
|
|
id: "simple-child-task",
|
|
run: async (payload, { ctx }) => {
|
|
// the run ID (and other useful info) is in ctx
|
|
const runId = ctx.run.id;
|
|
},
|
|
});
|
|
```
|
|
|
|
### Bulk replaying
|
|
|
|
You can replay multiple runs at once by selecting them from the table on the Runs page using the checkbox on the left hand side of the row. Then click the "Replay runs" button from the bulk action bar that appears at the bottom of the screen.
|
|
|
|
This is especially useful if you have lots of failed runs and want to run them all again. To do this, first filter the runs by the status you want, then select all the runs you want to replay and click the "Replay runs" button from the bulk action bar at the bottom of the page.
|
|
|
|
<video
|
|
src="https://content.trigger.dev/bulk-replaying-runs.mp4"
|
|
preload="auto"
|
|
controls={true}
|
|
loop
|
|
muted
|
|
autoPlay={true}
|
|
width="100%"
|
|
height="100%"
|
|
/> |