d336f79059
Before: a scheduled post hitting a platform outage was marked Failed — user had to manually retry. Now the job reschedules itself for 10 minutes later and the PostPlatform shows status "Retrying". Loops indefinitely until the platform accepts the post. - Adds PostPlatformStatus::Retrying (existing string column, no migration) - PublishToSocialPlatform: PlatformUnavailable catch now calls rescheduleForRetry() which (a) updates the row to Retrying with retry_count + next_attempt_at in error_context, and (b) dispatches itself with a 10-minute delay. updatePostStatus() naturally leaves the parent Post in Publishing because Retrying is neither Published nor Failed. - Same treatment for the retry-refresh edge case (publisher throws TokenExpired, refresh subsequently fails with PlatformUnavailable). - i18n + frontend status config updated (en, pt-BR, es) for both posts.status.retrying and posts.edit.status.retrying. - Tests: 3 new tests covering the dispatched job, the edge case path, and retry_count increment across attempts. |
||
|---|---|---|
| .. | ||
| components | ||
| composables | ||
| data | ||
| enums | ||
| layouts | ||
| lib | ||
| pages | ||
| types | ||
| utils | ||
| app.ts | ||
| datalayer.ts | ||
| date.ts | ||
| dayjs.ts | ||
| debounce.ts | ||
| posthog.ts | ||
| ssr.ts | ||